This playbook Remediates the Valid Accounts 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:
- T1078: Valid Accounts
Kill Chain phases:
- Defense Evasion
- Privilege Escalation
- Initial Access
MITRE ATT&CK Description:
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Compromised credentials may be used to bypass access controls placed on various resources on systems within the network and may even be used for persistent access to remote systems and externally available services, such as VPNs, Outlook Web Access and remote desktop. Compromised credentials may also grant an adversary increased privilege to specific systems or access to restricted areas of the network. Adversaries may choose not to use malware or tools in conjunction with the legitimate access those credentials provide to make it harder to detect their presence.
The overlap of permissions for local, domain, and cloud accounts across a network of systems is of concern because the adversary may be able to pivot across accounts and systems to reach a high level of access (i.e., domain or enterprise administrator) to bypass access controls set within the enterprise.
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.
This playbook uses the following sub-playbooks, integrations, and scripts.
- PAN-OS - Enforce URL Filtering Best Practices Profile
This playbook does not use any integrations.
This playbook does not use any commands.
|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 results.||Optional|
|Handled.Techniques||The technique handled in this playbook||unknown|