Fix T1551 to T1070 (#1161)
* Fix T1551 to T1070 Found that we had T1070 labeled incorrectly as T1551. MITRE pushed a fix for this per https://attack.mitre.org/resources/updates/updates-july-2020/ ``` Indicator Removal on Host Was incorrectly re-IDd to T1551, restored to T1070 and its sub-techniques were changed to T1070.001, T1070.002, T1070.003, T1070.004, T1070.005, and T1070.006 ``` * Generate MD fix Attempting to get the MD to generate * Update enterprise-attack.json * Generate docs from job=validate_atomics_generate_docs branch=T1070-indicator-removal-fix Co-authored-by: CircleCI Atomic Red Team doc generator <email>
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# T1518 - Software Discovery
|
||||
## [Description from ATT&CK](https://attack.mitre.org/wiki/Technique/T1518)
|
||||
<blockquote>Adversaries may attempt to get a listing of software and software versions that are installed on a system. Adversaries may use the information from [Software Discovery](https://attack.mitre.org/techniques/T1518) during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.
|
||||
<blockquote>Adversaries may attempt to get a listing of software and software versions that are installed on a system or in a cloud environment. Adversaries may use the information from [Software Discovery](https://attack.mitre.org/techniques/T1518) during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.
|
||||
|
||||
Adversaries may attempt to enumerate software for a variety of reasons, such as figuring out what security measures are present or if the compromised system has a version of software that is vulnerable to [Exploitation for Privilege Escalation](https://attack.mitre.org/techniques/T1068).</blockquote>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user