Tutorial: Azure AD SSO integration with Guardium Data Protection

In this tutorial, you'll learn how to integrate Guardium Data Protection with Azure Active Directory (Azure AD). When you integrate Guardium Data Protection with Azure AD, you can:

  • Control in Azure AD who has access to Guardium Data Protection.
  • Enable your users to be automatically signed-in to Guardium Data Protection with their Azure AD accounts.
  • Manage your accounts in one central location - the Azure portal.

Prerequisites

To get started, you need the following items:

  • An Azure AD subscription. If you don't have a subscription, you can get a free account.
  • Guardium Data Protection single sign-on (SSO) enabled subscription.
  • Along with Cloud Application Administrator, Application Administrator can also add or manage applications in Azure AD. For more information, see Azure built-in roles.

Scenario description

In this tutorial, you configure and test Azure AD SSO in a test environment.

  • Guardium Data Protection supports SP and IDP initiated SSO.

To configure the integration of Guardium Data Protection into Azure AD, you need to add Guardium Data Protection from the gallery to your list of managed SaaS apps.

  1. Sign in to the Azure portal using either a work or school account, or a personal Microsoft account.
  2. On the left navigation pane, select the Azure Active Directory service.
  3. Navigate to Enterprise Applications and then select All Applications.
  4. To add new application, select New application.
  5. In the Add from the gallery section, type Guardium Data Protection in the search box.
  6. Select Guardium Data Protection from results panel and then add the app. Wait a few seconds while the app is added to your tenant.

Configure and test Azure AD SSO for Guardium Data Protection

Configure and test Azure AD SSO with Guardium Data Protection using a test user called B.Simon. For SSO to work, you need to establish a link relationship between an Azure AD user and the related user in Guardium Data Protection.

To configure and test Azure AD SSO with Guardium Data Protection, perform the following steps:

  1. Configure Azure AD SSO - to enable your users to use this feature.
    1. Create an Azure AD test user - to test Azure AD single sign-on with B.Simon.
    2. Assign the Azure AD test user - to enable B.Simon to use Azure AD single sign-on.
  2. Configure Guardium Data Protection SSO - to configure the single sign-on settings on application side.
    1. Create Guardium Data Protection test user - to have a counterpart of B.Simon in Guardium Data Protection that is linked to the Azure AD representation of user.
  3. Test SSO - to verify whether the configuration works.

Configure Azure AD SSO

Follow these steps to enable Azure AD SSO in the Azure portal.

  1. In the Azure portal, on the Guardium Data Protection application integration page, find the Manage section and select single sign-on.

  2. On the Select a single sign-on method page, select SAML.

  3. On the Set up single sign-on with SAML page, click the pencil icon for Basic SAML Configuration to edit the settings.

    Screenshot shows to edit Basic S A M L Configuration.

  4. On the Basic SAML Configuration section, perform the following steps:

    a. In the Identifier text box, type a value using the following pattern: <hostname>

    b. In the Reply URL text box, type a URL using the following pattern: https://<hostname>:8443/saml/sso

  5. Click Set additional URLs and perform the following step if you wish to configure the application in SP initiated mode:

    In the Sign-on URL text box, type a URL using the following pattern: https://<hostname>:8443

    Note

    These values are not real. Update these values with the actual Identifier, Reply URL and Sign-on URL. Contact Guardium Data Protection support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.

  6. Guardium Data Protection application expects the SAML assertions in a specific format, which requires you to add custom attribute mappings to your SAML token attributes configuration. The following screenshot shows the list of default attributes.

    Screenshot shows the Guardium Data Protection application image.

  7. In addition to above, Guardium Data Protection application expects few more attributes to be passed back in SAML response, which are shown below. These attributes are also pre populated but you can review them as per your requirement.

    Name Source Attribute
    jobtitle user.jobtitle
  8. On the Set-up single sign-on with SAML page, in the SAML Signing Certificate section, find Federation Metadata XML and select Download to download the certificate and save it on your computer.

    Screenshot shows the Certificate download link.

  9. On the Set up Guardium Data Protection section, copy the appropriate URL(s) based on your requirement.

    Screenshot shows to copy configuration appropriate U R L.

Create an Azure AD test user

In this section, you'll create a test user in the Azure portal called B.Simon.

  1. From the left pane in the Azure portal, select Azure Active Directory, select Users, and then select All users.
  2. Select New user at the top of the screen.
  3. In the User properties, follow these steps:
    1. In the Name field, enter B.Simon.
    2. In the User name field, enter the username@companydomain.extension. For example, B.Simon@contoso.com.
    3. Select the Show password check box, and then write down the value that's displayed in the Password box.
    4. Click Create.

Assign the Azure AD test user

In this section, you'll enable B.Simon to use Azure single sign-on by granting access to Guardium Data Protection.

  1. In the Azure portal, select Enterprise Applications, and then select All applications.
  2. In the applications list, select Guardium Data Protection.
  3. In the app's overview page, find the Manage section and select Users and groups.
  4. Select Add user, then select Users and groups in the Add Assignment dialog.
  5. In the Users and groups dialog, select B.Simon from the Users list, then click the Select button at the bottom of the screen.
  6. If you are expecting a role to be assigned to the users, you can select it from the Select a role dropdown. If no role has been set up for this app, you see "Default Access" role selected.
  7. In the Add Assignment dialog, click the Assign button.

Configure Guardium Data Protection SSO

To configure single sign-on on Guardium Data Protection side, you need to send the downloaded Federation Metadata XML and appropriate copied URLs from Azure portal to Guardium Data Protection support team. They set this setting to have the SAML SSO connection set properly on both sides.

Create Guardium Data Protection test user

In this section, you create a user called Britta Simon in Guardium Data Protection. Work with Guardium Data Protection support team to add the users in the Guardium Data Protection platform. Users must be created and activated before you use single sign-on.

Test SSO

In this section, you test your Azure AD single sign-on configuration with following options.

SP initiated:

  • Click on Test this application in Azure portal. This will redirect to Guardium Data Protection Sign on URL where you can initiate the login flow.

  • Go to Guardium Data Protection Sign-on URL directly and initiate the login flow from there.

IDP initiated:

  • Click on Test this application in Azure portal and you should be automatically signed in to the Guardium Data Protection for which you set up the SSO.

You can also use Microsoft My Apps to test the application in any mode. When you click the Guardium Data Protection tile in the My Apps, if configured in SP mode you would be redirected to the application sign on page for initiating the login flow and if configured in IDP mode, you should be automatically signed in to the Guardium Data Protection for which you set up the SSO. For more information about the My Apps, see Introduction to the My Apps.

Next steps

Once you configure Guardium Data Protection you can enforce session control, which protects exfiltration and infiltration of your organization’s sensitive data in real time. Session control extends from Conditional Access. Learn how to enforce session control with Microsoft Cloud App Security.