Configure Integration Between Oracle Access Governance and Prisma Cloud

You can establish a connection between Oracle Access Governance and Prisma Cloud application as a Managed System. To configure, use Orchestrated Systems in the Oracle Access Governance Console.

Prerequisites - Setting up SCIM Connector in the Cloud Identity Engine application

To enable SCIM operations for your application, refer the following prerequisites.

Configure your directory to use the SCIM Connector with the Palo Alto Network's Cloud Identity Engine application.

In the Cloud Identity Engine app, select Directory SyncDirectoriesCloud DirectorySet UpSCIM

  1. In the Cloud Identity Engine application, go to Directories, and then select Sync Directories.
  2. From the Cloud Directory section, in the Set Up list, select SCIM.
  3. In the SCIM Client list, select Others.
  4. Enter Directory ID. For example 12345678-access-governance
  5. Enter Directory Name. For example access-governance-scim-client
  6. Copy the base URL and save it.
  7. Select Generate Token and save the Authorization Token. you'll need this later for configuration
  8. Select Submit.
  9. Click OK to confirm your acknowledgment.
You can now configure the Prisma Cloud orchestrated system by entering the Base URL and Authorization Token in your Oracle Access Governance service instance.

Configure

You can establish a connection between Prisma Cloud and Oracle Access Governance by entering connection details. To achieve this, use the orchestrated systems functionality available in the Oracle Access Governance Console.

Navigate to the Orchestrated Systems Page

The Orchestrated Systems page of the Oracle Access Governance Console is where you start configuration of your orchestrated system.

Navigate to the Orchestrated Systems page of the Oracle Access Governance Console, by following these steps:
  1. From the Oracle Access Governance navigation menu icon Navigation menu, select Service Administration → Orchestrated Systems.
  2. Click the Add an orchestrated system button to start the workflow.

Add details

Add details such as name, description, and configuration mode.

On the Add Details step of the workflow, enter the details for the orchestrated system:
  1. Enter a name for the system you want to connect to in the Name field.
  2. Enter a description for the system in the Description field. For this orchestrated system, Oracle Access Governance can manage permissions
  3. Click Next.

Add Owners

Add primary and additional owners to your orchestrated system to allow them to manage resources.

You can associate resource ownership by adding primary and additional owners. This drives self-service as these owners can then manage (read, update or delete) the resources that they own. By default, the resource creator is designated as the resource owner. You can assign one primary owner and up to 20 additional owners for the resources.

Note:

When setting up the first Orchestrated System for your service instance, you can assign owners only after you enable the identities from the Manage Identities section.
To add owners:
  1. Select an Oracle Access Governance active user as the primary owner in the Who is the primary owner? field.
  2. Select one or more additional owners in the Who else owns it? list. You can add up to 20 additional owners for the resource.
You can view the Primary Owner in the list. All the owners can view and manage the resources that they own.

Account settings

Outline details of how to manage account settings when setting up your orchestrated system including notification settings, and default actions when an identity moves or leaves your organization.

On the Account settings step of the workflow, enter details of how you would like to manage accounts with Oracle Access Governance when configured as a managed system:
  1. Select to allow Oracle Access Governance to create new accounts when a permission is requested, if the account does not already exist. By default this option is selected meaning that an account will be created if it does not exist, when a permission is requested. If the option is unselected then permissions can only be provisioned where the account already exists in the orchestrated system. If permission is requested where no user exists then the provisioning operation will fail.
  2. Select where and who to send notification emails when an account is created. The default setting is User. You can select one, both, or none of these options. If you select no options then notifications will not be sent when an account is created.
    • User
    • User manager
  3. When an identity leaves your enterprise you should remove access to their accounts. You can select what to do with the account when this happens. Select one of the following options:
    • Delete: Deletes all accounts and permissions managed by Oracle Access Governance.
    • Disable: Disables all accounts and marks permissions as Inactive for all permissions managed by Oracle Access Governance.
      • Delete the permissions for disabled accounts: To ensure zero residual access, select this to delete directly assigned permissions and policy-granted permissions during account disablement.
    • No action: No action is taken when an identity leaves the organization by Oracle Access Governance.

    Note:

    The options above are only displayed if supported in the orchestrated system type being configured. For example, if Delete is not supported, then you will only see the Disable and No action options.
  4. When all permissions for an account are removed, for example when moving from one department to another, you may need to adjust what accounts the identity has access to. You can select what to do with the account when this happens. Select one of the following options:
    • Delete
    • Disable
    • No action

    Note:

    The options above are only displayed if supported in the orchestrated system type being configured. For example, if Delete is not supported, then you will only see the Disable and No action options.
  5. If you want Oracle Access Governance to manage accounts created directly in the orchestrated system you can select the Manage accounts that are not created by Access Governance option. This will reconcile accounts created in the managed system and will allow you to manage them from Oracle Access Governance.

Note:

If you do not configure your system as a managed system then this step in the workflow will display but is not enabled. In this case you proceed directly to the Integration settings step of the workflow.

Note:

If your orchestrated system requires dynamic schema discovery, as with the Generic REST and Database Application Tables integrations, then only the notification email destination can be set (User, Usermanager) when creating the orchestrated system. You cannot set the disable/delete rules for movers and leavers. To do this you need to create the orchestrated system, and then update the account settings as described in Configure Orchestrated System Account Settings.

Integration settings

Enter details of the connection to your Prisma Cloud system.

  1. Complete the prerequisites. See Prerequisites - Setting up SCIM Connector in the Cloud Identity Engine application.
  2. On the Integration settings step of the workflow, enter the details required to allow Oracle Access Governance to connect to your Prisma Cloud system.

    Table - Integration settings

    Parameter Name Description

    Prisma Cloud Host Name

    		 Base URL to access your Prisma Cloud application. For example:
    <https://<tenant>.apps.paloaltonetworks.com/scim/v2
    Authentication Header Enter the OAuth 2.0 access token in the format. 
    access_token=<access_token_value>
    .
  3. Click Add to create the orchestrated system.

Finish Up

Finish up configuration of your orchestrated system by providing details of whether to perform further customization, or activate and run a data load.

The final step of the workflow is Finish Up.

You are given a choice whether to further configure your orchestrated system before running a data load, or accept the default configuration and initiate a data load. Select one from:
  • Customize before enabling the system for data loads
  • Activate and prepare the data load with the provided defaults

Post Configuration

There are no post configuration steps associated with the Prisma Cloud system.