Attempt To Set Default Powershell Execution Policy To Unrestricted Or Bypass

Description

Monitor for changes of the ExecutionPolicy in the registry to the values "unrestricted" or "bypass," which allows the execution of malicious scripts.

Content Mapping

This content is not mapped to any local saved search. Add mapping


Use Case

Advanced Threat Detection

Category

Adversary Tactics,

Alert Volume

Monitor for changes of the ExecutionPolicy in the registry to the values "unrestricted" or "bypass," which allows the execution of malicious scripts.

SPL Difficulty

None

Journey

Stage 3

MITRE ATT&CK Tactics

Execution

MITRE ATT&CK Techniques

Command and Scripting Interpreter

PowerShell

MITRE Threat Groups

APT19
APT28
APT29
APT3
APT32
APT33
APT39
APT41
BRONZE BUTLER
Blue Mockingbird
Chimera
Cobalt Group
CopyKittens
DarkHydrus
DarkVishnya
Deep Panda
Dragonfly 2.0
FIN10
FIN6
FIN7
FIN8
Frankenstein
Gallmaker
Gorgon Group
Inception
Kimsuky
Lazarus Group
Leviathan
Magic Hound
Molerats
MuddyWater
OilRig
Patchwork
Poseidon Group
Silence
Soft Cell
Stealth Falcon
TA459
TA505
TEMP.Veles
Threat Group-3390
Thrip
Turla
WIRTE
Wizard Spider
menuPass

Kill Chain Phases

Installation
Actions On Objectives

Data Sources

Endpoint Detection and Response

   Help

Attempt To Set Default Powershell Execution Policy To Unrestricted Or Bypass Help

You must be ingesting data that records process activity from your hosts to populate the Endpoint data model in the Registry node. You must also be ingesting logs with the fields registrypath, registrykeyname, and registryvalue_name from your endpoints.

   Search

Open in Search