t1136 | LoFP

t1136

Title	Tags
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.	t1136 aws elastic
admin activity	t1033 t1059 t1059.004 t1070 t1070.001 t1136 t1136.001 t1485 t1505 t1505.003 t1546 t1546.001 t1562 t1562.002 t1562.004 windows linux sigma
administrative activity	t1003 t1016 t1021 t1021.001 t1027 t1036 t1053 t1053.005 t1059 t1059.001 t1059.005 t1071 t1071.001 t1087 t1087.001 t1087.002 t1098 t1105 t1133 t1134 t1136 t1136.001 t1137 t1222 t1222.001 t1505 t1505.004 t1552 t1552.006 t1555 t1555.004 t1562 t1562.001 t1572 t1615 windows linux sigma
administrator or network operator can execute this command. please update the filter macros to remove false positives.	t1003 T1003.008 t1016 t1070 t1070.004 t1136 t1136.001 t1222 t1222.002 t1485 t1547 t1547.006 t1548 t1548.001 t1548.003 t1574 t1574.006 endpoint splunk
administrator or network operator can use this application for automation purposes. please update the filter macros to remove false positives.	t1016 t1030 t1033 t1053 t1053.002 t1053.003 t1083 t1136 t1136.001 t1140 t1222 t1222.002 t1485 t1489 t1546 t1546.004 t1547 t1547.006 t1552 t1552.004 t1555 t1555.005 t1562 t1562.004 t1569 t1569.002 t1574 t1574.006 endpoint splunk
administrators may legitimately create azure automation accounts. filter as needed.	t1136 t1136.003 azure tenant splunk
administrators may legitimately create azure automation runbooks. filter as needed.	t1136 t1136.003 azure tenant splunk
administrators often leverage net.exe to create admin accounts.	t1136 t1136.001 endpoint splunk
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.	t1136 aws elastic
assumed roles may be used by legitimate automated systems to create iam users for specific workflows. verify if this event aligns with known automation activities. if the action is routine for specific roles or user agents (e.g., `aws-cli`, `boto3`), consider adding those roles or user agents to a monitored exception list for streamlined review.	t1136 aws elastic
better use event ids for user creation rather than command line rules.	t1136 t1136.001 windows sigma
domain controller logs	t1136 t1136.001 windows sigma
if the behavior of creating okta api tokens is expected, consider adding exceptions to this rule to filter false positives.	t1136 okta elastic
it is possible that an administrator created and deleted an account in a short time period. verifying activity with an administrator is advised.	t1078.003 t1136 t1136.001 windows splunk
it is possible that an administrator created the account. verifying activity with an administrator is advised. this analytic is set to anomaly to allow for risk to be added. filter and tune as needed. restrict to critical infrastructure to reduce any volume.	t1136 t1136.001 endpoint splunk
legitimate administration activities	t1007 t1016 t1018 t1033 t1037 t1037.005 t1040 t1046 t1053 t1053.002 t1053.003 t1069 t1069.001 t1070 t1070.002 t1070.004 t1078 t1078.003 t1082 t1087 t1087.001 t1090 t1105 t1136 t1136.001 t1140 t1201 t1518 t1518.001 t1546 t1546.014 t1548 t1548.001 t1552 t1552.001 t1553 t1553.004 t1555 t1555.001 t1562 t1562.004 t1564 t1564.002 t1565 t1565.001 t1592 t1592.004 windows macos linux sigma
legitimate administrative script	t1059 t1059.001 t1098 t1132 t1132.001 t1136 t1136.002 t1553 t1553.004 t1571 t1573 t1574 t1574.011 t1574.012 windows sigma
legitimate local user creations may be done by a system or network administrator. verify whether this is known behavior in your environment. local user creations by unfamiliar users or hosts should be investigated. if known behavior is causing false positives, it can be exempted from the rule.	t1136 windows elastic
legitimate user creation.	t1136 t1136.001 windows sigma
local accounts managed by privileged account management tools	t1136 t1136.001 windows sigma
organization approved new members	t1136 t1136.003 github sigma
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.	t1136 gcp elastic
the activity may be legitimate. for this reason, it's best to verify the account with an administrator and ask whether there was a valid service request for the account creation. if your local administrator group name is not \"administrators\", this search may generate an excessive number of false positives	t1136 t1136.001 windows splunk
the creation of a new federated domain is not necessarily malicious, however these events need to be followed closely, as it may indicate federated credential abuse or backdoor via federated identities at a similar or different cloud provider.	t1136 t1136.003 o365 tenant splunk
the creation of a new federation is not necessarily malicious, however these events need to be followed closely, as it may indicate federated credential abuse or backdoor via federated identities at a different cloud provider.	t1136 t1136.003 o365 tenant splunk
the creation of a new federation is not necessarily malicious, however this events need to be followed closely, as it may indicate federated credential abuse or backdoor via federated identities at a different cloud provider.	t1136 t1136.003 o365 tenant splunk
unlikely	t1003 t1003.001 t1003.002 t1003.004 t1003.005 t1003.006 t1005 t1007 t1008 t1012 t1014 t1016 t1018 t1021 t1021.002 t1021.003 t1021.006 t1027 t1027.005 t1033 t1036 t1036.003 t1036.005 t1036.007 t1041 t1046 t1047 t1048 t1048.001 t1053 t1053.003 t1053.005 t1055 t1055.001 t1056 t1057 t1059 t1059.001 t1059.002 t1059.003 t1068 t1070 t1071 t1071.001 t1071.004 t1078 t1082 t1083 t1087 t1090 t1090.001 t1090.003 t1105 t1106 t1112 t1115 t1123 t1127 t1132 t1132.001 t1133 t1134 t1134.001 t1134.002 t1134.004 t1136 t1136.001 t1136.002 t1137 t1137.002 t1140 t1190 t1202 t1203 t1204 t1210 t1213 t1213.003 t1216 t1218 t1218.001 t1218.008 t1218.010 t1218.011 t1218.013 t1219 t1486 t1489 t1490 t1496 t1498 t1499 t1499.001 t1505 t1505.003 t1526 t1528 t1543 t1543.003 t1546 t1546.008 t1546.015 t1548 t1548.003 t1550 t1550.003 t1552 t1552.004 t1553 t1553.004 t1555 t1556 t1557 t1557.001 t1558 t1558.003 t1562 t1562.001 t1562.002 t1562.010 t1564 t1564.004 t1566 t1569 t1569.002 t1570 t1574 t1574.001 t1574.002 t1586 t1587 t1587.001 t1588 t1588.002 t1590 t1590.001 t1590.002 t1620 t1649 windows opencanary okta m365 azure bitbucket macos linux sigma
when remote authentication is in place, this should not change often	t1098 t1136 t1136.001 cisco sigma
while this search has no known false positives, it is possible that an aws admin has legitimately created keys for another user.	t1078 t1136 t1136.003 aws account splunk