t1071 | LoFP

t1071

Title	Tags
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
administrative scripts that download files from the internet	t1071 t1071.001 sigma
administrative scripts that retrieve certain website contents	t1071 t1071.001 sigma
analyst testing	t1071 t1071.001 sigma
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.	t1059 t1071 macos elastic
false positives may be present. filter based on pipe name or process.	t1071 endpoint splunk
if you are seeing more results than desired, you may consider reducing the value for threshold in the search. you should also periodically re-run the support search to re-build the ml model on the latest data.	t1071 t1071.004 endpoint splunk
in modern windows systems, unable to see legitimate usage of this process, however, if an organization has legitimate purpose for this there can be false positives.	t1071 t1071.001 windows sigma
it is likely that the outbound server message block (smb) traffic is legitimate, if the company's internal networks are not well-defined in the assets and identity framework. categorize the internal cidr blocks as `internal` in the lookup file to avoid creating notable events for traffic destined to those cidr blocks. any other network connection that is going out to the internet should be investigated and blocked. best practices suggest preventing external communications of all smb versions and related protocols at the network boundary.	t1071 T1071.002 endpoint splunk
it is possible legitimate traffic can trigger this rule. please investigate as appropriate. the threshold for generating an event can also be customized to better suit your environment.	t1071 t1071.004 endpoint splunk
legitimate installation of code-tunnel as a service	t1071 t1071.001 windows sigma
legitimate software uses the scripts (preinstall, postinstall)	t1059 t1059.007 t1071 t1071.001 macos sigma
legitimate use of cloudflare tunnels will also trigger this.	t1071 t1071.001 windows sigma
legitimate use of devtunnels will also trigger this.	t1071 t1071.001 t1567 t1567.001 windows sigma
legitimate use of telegram bots in the company	t1071 t1071.001 t1102 t1102.002 sigma
legitimate use of visual studio code tunnel	t1071 t1071.001 windows sigma
legitimate use of visual studio code tunnel and running code from there	t1071 t1071.001 windows sigma
legitimate use of visual studio code tunnel will also trigger this.	t1071 t1071.001 t1567 t1567.001 windows sigma
legitimate webdav administration	t1071 t1071.001 sigma
old browsers	t1071 t1071.001 sigma
processes such as ms office using ieproxy to render html content.	t1071 t1559 windows elastic
rare programs that use bitsadmin and update from regional tlds e.g. .uk or .ca	t1071 t1071.001 t1197 sigma
scripts created by developers and admins	t1071 t1071.001 t1105 t1222 t1222.001 t1567 windows linux sigma
third party application may use this network protocol as part of its feature. filter is needed.	t1071 T1071.003 endpoint splunk
third party application may use this proxies if allowed in production environment. filter is needed.	t1071 T1071.003 endpoint splunk
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.	t1071 t1568 network elastic
this rule should be tailored to either exclude systems, as sources or destinations, in which this behavior is expected.	t1071 t1568 network elastic
this rule should be tailored to exclude systems, either as sources or destinations, in which this behavior is expected.	t1071 t1568 network elastic
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.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 t1203 t1204 t1210 t1213 t1213.003 t1216 t1218 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 t1548 t1548.003 t1550 t1550.003 t1552 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 bitbucket azure m365 okta macos windows linux opencanary sigma
user activity (e.g. developer that shared and copied code snippets and used the raw link instead of just copy & paste)	t1071 t1071.001 t1102 t1102.001 t1102.003 sigma
valid requests with this exact user agent to server scripts of the defined names	t1071 t1071.001 sigma
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.	t1071 ml elastic
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.	t1071 ml elastic