MITRE ATT&CK CoA - T1105 - Ingress tool transfer
MITRE ATT&CK - Courses of Action Pack.#
This Playbook is part of theSupported versions
Supported Cortex XSOAR versions: 6.5.0 and later.
This playbook Remediates the Ingress tool transfer technique using intelligence-driven Courses of Action (COA) defined by Palo Alto Networks Unit 42 team.
***Disclaimer: This playbook does not simulate an attack using the specified technique, but follows the steps to remediation as defined by Palo Alto Networks Unit 42 team’s Actionable Threat Objects and Mitigations (ATOMs). Techniques Handled:
- T1105: Ingress tool transfer
Kill Chain phases:
- Command And Control
MITRE ATT&CK Description: Adversaries may transfer tools or other files from an external system into a compromised environment. Files may be copied from an external adversary controlled system through the command and control channel to bring tools into the victim network or through alternate protocols with another tool such as FTP. Files can also be copied over on Mac and Linux with native tools like scp, rsync, and sftp.
Possible playbook uses:
- The playbook can be used independently to handle and remediate the specific technique.
- The playbook can be used as a part of the “Courses of Action - Defense Evasion” playbook to remediate techniques based on the kill chain phase.
- The playbook can be used as a part of the “MITRE ATT&CK - Courses of Action” playbook, which can be triggered by different sources and accepts the technique MITRE ATT&CK ID as an input.
#
DependenciesThis playbook uses the following sub-playbooks, integrations, and scripts.
#
Sub-playbooks- PAN-OS - Block all unknown and unauthorized applications
- PAN-OS - Enforce WildFire Best Practices Profile
#
IntegrationsThis playbook does not use any integrations.
#
Scripts- SetGridField
- IsIntegrationAvailable
- Set
#
CommandsThis playbook does not use any commands.
#
Playbook InputsName | Description | Default Value | Required |
---|---|---|---|
template | Template name to enforce WildFire best practices profile. | Optional | |
pre_post | Rules location. Can be 'pre-rulebase' or 'post-rulebase'. Mandatory for Panorama instances. | Optional | |
device-group | The device group for which to return addresses (Panorama instances). | Optional | |
tag | Tag for which to filter the rules. | Optional |
#
Playbook OutputsPath | Description | Type |
---|---|---|
Handled.Techniques | The techniques handled in this playbook | unknown |