From 85e799b37842ec237da08e00276d37eeb15b7a5d Mon Sep 17 00:00:00 2001 From: David French <56409778+threat-punter@users.noreply.github.com> Date: Thu, 3 Sep 2020 11:08:38 -0600 Subject: [PATCH] [New Rule] Azure Automation Account Created (#177) * new-rule-azure-automation-account-created * Fix rule name format :smile: * Update rules/azure/persistence_azure_automation_account_created.toml Update maturity to production * Update rules/azure/persistence_azure_automation_account_created.toml Update ecs_version to 1.6.0 Co-authored-by: Andrew Pease <7442091+peasead@users.noreply.github.com> Co-authored-by: Andrew Pease <7442091+peasead@users.noreply.github.com> --- ...ence_azure_automation_account_created.toml | 62 +++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 rules/azure/persistence_azure_automation_account_created.toml diff --git a/rules/azure/persistence_azure_automation_account_created.toml b/rules/azure/persistence_azure_automation_account_created.toml new file mode 100644 index 000000000..932944bdc --- /dev/null +++ b/rules/azure/persistence_azure_automation_account_created.toml @@ -0,0 +1,62 @@ +[metadata] +creation_date = "2020/08/18" +ecs_version = ["1.6.0"] +maturity = "production" +updated_date = "2020/08/18" + +[rule] +author = ["Elastic"] +description = """ +Identifies when an Azure Automation account is created. Azure Automation accounts can be used to automate management +tasks and orchestrate actions across systems. An adversary may create an Automation account in order to maintain +persistence in their target's environment. +""" +from = "now-25m" +index = ["filebeat-*"] +language = "kuery" +license = "Elastic License" +name = "Azure Automation Account Created" +note = "The Azure Filebeat module must be enabled to use this rule." +references = [ + "https://powerzure.readthedocs.io/en/latest/Functions/operational.html#create-backdoor", + "https://github.com/hausec/PowerZure", + "https://posts.specterops.io/attacking-azure-azure-ad-and-introducing-powerzure-ca70b330511a", + "https://azure.microsoft.com/en-in/blog/azure-automation-runbook-management/", +] +risk_score = 21 +rule_id = "df26fd74-1baa-4479-b42e-48da84642330" +severity = "low" +tags = ["Azure", "Continuous Monitoring", "Elastic", "Identity and Access", "SecOps"] +type = "query" + +query = ''' +event.module:azure and event.dataset:azure.activitylogs and event.category:Administrative and azure.activitylogs.operation_name:MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WRITE and event.outcome:Success +''' + + +[[rule.threat]] +framework = "MITRE ATT&CK" +[[rule.threat.technique]] +id = "T1078" +name = "Valid Accounts" +reference = "https://attack.mitre.org/techniques/T1078/" + + +[rule.threat.tactic] +id = "TA0003" +name = "Persistence" +reference = "https://attack.mitre.org/tactics/TA0003/" + + +[[rule.threat]] +framework = "MITRE ATT&CK" +[[rule.threat.technique]] +id = "T1078" +name = "Valid Accounts" +reference = "https://attack.mitre.org/techniques/T1078/" + + +[rule.threat.tactic] +id = "TA0005" +name = "Defense Evasion" +reference = "https://attack.mitre.org/tactics/TA0005/"