Azure-Sentinel/Playbooks/AS-Clear-Okta-Network-Zone-List

AS-Clear-Okta-Network-Zone-List

Author: Accelerynt

For any technical questions, please contact info@accelerynt.com

This playbook is intended to be run on a schedule. It will clear out all but one of the IPs from an Okta Network Zone list (leaving at least one entry is required by API). This will prevent the list from reaching capacity. This may be desired because lists at capacity inhibit newer entries from being added.

Requirements

The following items are required under the template settings during deployment:

• An Okta Admin account and API token
• An Okta Network Zone to add IPs to
• An Azure Key Vault Secret containing your Okta API Token

Setup

Create an Azure Key Vault Secret:

Navigate to the Azure Key Vaults page: https://portal.azure.com/#view/HubsExtension/BrowseResource/resourceType/Microsoft.KeyVault%2Fvaults

Navigate to an existing Key Vault or create a new one. From the Key Vault overview page, click the "Secrets" menu option, found under the "Settings" section. Click "Generate/Import".

Choose a name for the secret, such as "AS-Clear-Okta-Network-Zone-List-API-Token", and enter the Okta API Token copied previously in the "Value" field. All other settings can be left as is. Click "Create".

Once your secret has been added to the vault, navigate to the "Access policies" menu option, also found under the "Settings" section on the Key Vault page menu. Leave this page open, as you will need to return to it once the playbook has been deployed. See Granting Access to Azure Key Vault.

Deployment

To configure and deploy this playbook:

Open your browser and ensure you are logged into your Microsoft Sentinel workspace. In a separate tab, open the link to our playbook on the Accelerynt Security GitHub Repository:

https://github.com/Accelerynt-Security/AS-Clear-Okta-Network-Zone-List

Click the “Deploy to Azure” button at the bottom and it will bring you to the custom deployment template.

In the Project Details section:

• Select the “Subscription” and “Resource Group” from the dropdown boxes you would like the playbook deployed to.

In the Instance Details section:

• Playbook Name: This can be left as "AS-Clear-Okta-Network-Zone-List" or you may change it.

• Okta Subdomain: Enter the name of the subdomain (tenant) in the Okta Org URL. For example, with the URL https://example-admin.okta.com/, "example-admin" would be entered here.

• Okta Network Zone: Enter the name of the Okta Network Zone to be cleared.

• Key Vault Name: Enter the name of the Key Vault referenced in Create an Azure Key Vault Secret.

• Secret Name: Enter the name of the Key Vault Secret created in Create an Azure Key Vault Secret.

Towards the bottom, click on “Review + create”.

Once the resources have validated, click on "Create".

The resources should take around a minute to deploy. Once the deployment is complete, you can expand the "Deployment details" section to view them. Click the one corresponding to the Logic App.

Granting Access to Azure Key Vault

Before the Logic App can run successfully, the Key Vault connection created during deployment must be granted access to the Key Vault storing your Okta API Token.

From the Key Vault "Access policies" page, click "Create".

Select the "Get" checkbox under "Secret permissions", then click "Next".

Paste "AS-Clear-Okta-Network-Zone-List" into the principal search box and click the option that appears. Click "Next" towards the bottom of the page.

Navigate to the "Review + create" section and click "Create".