markeytos / CloudWatcher

Checks our resources to monitor Identity Changes

Cloud Watcher

Cloud Watcher is an Open Source script that scans your subscription and compares it to a baseline, this helps companies reduce the time to detect breaches to their cloud resources.

Requirements

• Azure Account
• Azure Automation Service with runas service principal
• Storage Account

In Scope

Azure has an ever growing number of resources and features, making it impossible for us to cover all of them, we currently monitor the following actions and resources:

• RBAC Changes to subscriptions
• Classic Administrator changes to subscriptions
• Azure Resource Provider changes to subscription
• Resource creation or deletion
• Change of Group membership (just first degree, we do not support nested groups)
• SQL Firewall changes
• SQL Server AAD Admin changes
• AKV Access Policies Changes
• AKV Firewall changes

Installation Instructions

AAD App Creation and Setup

1. Create Azure Automation Account with runas account

2. Give the service principal created reader access to the subscriptions you want to monitor.

3. Go to Azure Active Directory > Enterprise Applications and select the application created as the runas account. (you might have to change the filter to all applications and search for the name of your application)

4. Copy the object ID shown in the application page.

5. Get the Directory Readers Role ID running 'Get-AzureADDirectoryRole'

6. Run the following commands replacing with the app's object Id. and the role ID with the 'Directory readers' role ID.

$roleID = '<Role ID>'
$appObjID = '<APP ObjectID>'
Connect-AzureAD
Add-AzureADDirectoryRoleMember -ObjectId $roleID  -RefObjectId  $appObjID

Storage Account Setup

Before setting this up, please read the "Recommended Use" section since we have some security recommendations as on where to set up this storage account.

1. Create a storage account.

2. Create a container to hold your baseline

Runbook Setup

Variable Setup

1. In the Azure portal, go to the Azure Automation Account you created in the first section.

2. Go to Variables (under the Share Resources section)

3. Create a variable named "accountName" with the storage account name as the value.

4. Create a variable named "blobName" with a name for the baseline file (we use "baseline.json") as the value.

5. Create a variable named "containerName" with the storage account container name as the value.

6. Create a variable named "RunType" This value is used to tell the script if you are running in monitoring mode or Baselining mode. enter "monitoring" or "baseline" as the value depending on which mode you want to run.

7. Create a variable named "accountKey" with the storage account SAS key as the value Remember to set this value as encrypted!

Adding Modules

In the Azure Automation Resource, go to modules, and add the following modules:

• Az.KeyVault

• Az.Resources

• Az.Sql

• Az.Storage

• Az.Accounts

Runbook Setup

Now that we have set up the script to run.

1. In the Azure Automation account, go to runbooks.

2. Click on "Browse Gallery"

3. In the search field type "CloudWatcher"

4. Select the CloudWatcher created by "markeytos"

5. Click Import

6. Enter the name for your Runbook

7. This should add the runbook in your runbook list:

8. Click on it and click the edit button.

9. Once the editor is open, click the test pane and run the test to make sure it is working properly. Note: The fist time you run it you should set the run type as baseline to have a baseline in the storage account.

10. If the run is successful, go back to the edit pane and click on publish: Your Runbook should now be published and it should allow you to add it to schedules.

Installation Video Tutorial

https://youtu.be/z4aY8kFKo8M

Recommended Use

For security reasons we recommend running the automation account, and hosting the storage account in a different subscription than the subscription being hosted. This prevents attackers that get access to your subscription to stop or modify the baseline.

How Did We Set It Up

At Keytos we wanted to ensure the security of our CloudWatcher deployment. To do this we use 3 different subscriptions, and they all point at each other with CloudWatchers.

To simplify it I am just going to show one of the CloudWatchers in the diagram.

The Idea is that you have the subscription that you want to monitor (Subscription A). Then in a different subscription (Subscription B) that ideally does not share any of the same administrator identities with the subscription you want to monitor, you create the CloudWatcher Automation Account. Then in another Subscription (Subscription C) (At Keytos we do it in another Tenant) you have a storage account with the baseline. The token given to the CloudWatcher in Subscription B only has read access to the baseline blob, meaning that a compromise of that account does not allow to make changes to the baseline.