{ "id": "c5db6c1d-a462-4a66-abce-3023a12710fc", "created_at": "2026-04-06T02:11:32.669684Z", "updated_at": "2026-04-10T03:24:29.353789Z", "deleted_at": null, "sha1_hash": "9adf186cb8c9dbce3c20e3642531d907effab218", "title": "CAPEC-578: Disable Security Software (Version 3.9)", "llm_title": "", "authors": "", "file_creation_date": "0001-01-01T00:00:00Z", "file_modification_date": "0001-01-01T00:00:00Z", "file_size": 44631, "plain_text": "CAPEC-578: Disable Security Software (Version 3.9)\r\nArchived: 2026-04-06 01:57:53 UTC\r\nAttack Pattern ID: 578\r\nAbstraction: Standard\r\n Description\r\nAn adversary exploits a weakness in access control to disable security tools so that detection does not occur. This can take\r\nthe form of killing processes, deleting registry keys so that tools do not start at run time, deleting log files, or other methods.\r\n Likelihood Of Attack\r\nMedium\r\n Typical Severity\r\nMedium\r\n Relationships\r\nThis table shows the other attack patterns and high level categories that are related to this attack pattern. These\r\nrelationships are defined as ChildOf and ParentOf, and give insight to similar items that may exist at higher and lower levels\r\nof abstraction. In addition, relationships such as CanFollow, PeerOf, and CanAlsoBe are defined to show similar attack\r\npatterns that the user may want to explore.\r\nNature Type\r\nChildOf Meta Attack Pattern - A meta level attack pattern in CAPEC is a decidedly abstract characterization of a specific methodology or techniqu\r\nThis table shows the views that this attack pattern belongs to and top level categories within that view.\r\nView Name Top Level Categories\r\nDomains of Attack Software\r\nMechanisms of Attack Manipulate System Resources\r\n Prerequisites\r\nThe adversary must have the capability to interact with the configuration of the targeted system.\r\n Resources Required\r\nNone: No specialized resources are required to execute this type of attack.\r\n Consequences\r\nThis table specifies different individual consequences associated with the attack pattern. The Scope identifies the security\r\nproperty that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in\r\ntheir attack. The Likelihood provides information about how likely the specific consequence is expected to be seen relative\r\nto the other consequences in the list. For example, there may be high likelihood that a pattern will be used to achieve a\r\ncertain impact, but a low likelihood that it will be exploited to achieve a different impact.\r\nScope Impact Likelihood\r\nAvailability Hide Activities\r\n Mitigations\r\nEnsure proper permissions are in place to prevent adversaries from altering the execution status of security tools.\r\n Taxonomy Mappings\r\nhttps://capec.mitre.org/data/definitions/578.html\r\nPage 1 of 2\n\nCAPEC mappings to ATT\u0026CK techniques leverage an inheritance model to streamline and minimize direct\r\nCAPEC/ATT\u0026CK mappings. Inheritance of a mapping is indicated by text stating that the parent CAPEC has relevant\r\nATT\u0026CK mappings. Note that the ATT\u0026CK Enterprise Framework does not use an inheritance model as part of the\r\nmapping to CAPEC.\r\nRelevant to the ATT\u0026CK taxonomy mapping\r\nEntry ID Entry Name\r\n1556.006 Modify Authentication Process: Multi-Factor Authentication\r\n1562.001 Impair Defenses: Disable or Modify Tools\r\n1562.002 Impair Defenses: Disable Windows Event Logging\r\n1562.004 Impair Defenses: Disable or Modify System Firewall\r\n1562.007 Impair Defenses: Disable or Modify Cloud Firewall\r\n1562.008 Impair Defenses: Disable Cloud Logs\r\n1562.009 Impair Defenses: Safe Mode Boot\r\n Content History\r\nSubmissions\r\nSubmission\r\nDate\r\nSubmitter Organization\r\n2015-11-09\r\n(Version 2.7)\r\nCAPEC Content Team The MITRE Corporation\r\nModifications\r\nModification\r\nDate\r\nModifier Organization\r\n2018-07-31\r\n(Version 2.12)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Attack_Motivation-Consequences, Attack_Prerequisites, Description Summary, References,\r\nRelated_Weaknesses, Resources_Required, Solutions_and_Mitigations,\r\nTypical_Likelihood_of_Exploit, Typical_Severity\r\n2019-04-04\r\n(Version 3.1)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Related_Weaknesses\r\n2019-09-30\r\n(Version 3.2)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Related_Attack_Patterns\r\n2020-07-30\r\n(Version 3.3)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Related_Attack_Patterns, Taxonomy_Mappings\r\n2022-09-29\r\n(Version 3.8)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Taxonomy_Mappings\r\n2023-01-24\r\n(Version 3.9)\r\nCAPEC Content Team The MITRE Corporation\r\nUpdated Taxonomy_Mappings\r\nMore information is available — Please select a different filter.\r\nSource: https://capec.mitre.org/data/definitions/578.html\r\nhttps://capec.mitre.org/data/definitions/578.html\r\nPage 2 of 2", "extraction_quality": 1, "language": "EN", "sources": [ "MITRE" ], "references": [ "https://capec.mitre.org/data/definitions/578.html" ], "report_names": [ "578.html" ], "threat_actors": [ { "id": "aa73cd6a-868c-4ae4-a5b2-7cb2c5ad1e9d", "created_at": "2022-10-25T16:07:24.139848Z", "updated_at": "2026-04-10T02:00:04.878798Z", "deleted_at": null, "main_name": "Safe", "aliases": [], "source_name": "ETDA:Safe", "tools": [ "DebugView", "LZ77", "OpenDoc", "SafeDisk", "TypeConfig", "UPXShell", "UsbDoc", "UsbExe" ], "source_id": "ETDA", "reports": null } ], "ts_created_at": 1775441492, "ts_updated_at": 1775791469, "ts_creation_date": 0, "ts_modification_date": 0, "files": { "pdf": "https://archive.orkl.eu/9adf186cb8c9dbce3c20e3642531d907effab218.pdf", "text": "https://archive.orkl.eu/9adf186cb8c9dbce3c20e3642531d907effab218.txt", "img": "https://archive.orkl.eu/9adf186cb8c9dbce3c20e3642531d907effab218.jpg" } }