Nailing the Security Audit with RRCU

ConductorOne docs

Set up a NetSuite connector

ConductorOne provides identity governance for Oracle NetSuite. Integrate your NetSuite instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

  • Sync user identities from NetSuite to ConductorOne

  • Resources supported:

    • Roles

Add a new NetSuite connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

  1. In ConductorOne, click Connectors > Add connector.

  2. Search for NetSuite and click Add.

  3. Choose how to set up the new NetSuite connector:

    • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

    • Add the connector to a managed app (select from the list of existing managed apps)

    • Create a new managed app

    Do you SSO into NetSuite using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged NetSuite app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.

  1. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

    A NetSuite connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • Administrator role in NetSuite
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your NetSuite connector for instructions on integrating NetSuite with ConductorOne.

  • If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your NetSuite connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and an Administrator role in NetSuite must perform this task.

Before you begin: Make sure you have enabled the following features for your NetSuite instance:

  • Token-Based Authentication
  • REST Web Services
  • Suite Analytics Workbook

You’ll find directions for enabling features in the NetSuite documentation.

Step 1: Locate your NetSuite Account ID

  1. In NetSuite, navigate to Setup > Company > Company Information.

  2. Find the ACCOUNT ID field on the page. Make a note of your account ID. We’ll use it in Step 5.

Step 2: Generate a consumer key and consumer secret

  1. In NetSuite, navigate to Setup > Integrations > Manage Integrations. Click New to create a new integration.

  2. Give the new integration a name, such as “ConductorOne”.

  3. Check the box for TOKEN-BASED AUTHENTICATION.

  4. Click Save. The new integration is created, and its consumer key and consumer secret are shown.

  5. Make a careful note of these credentials (they won’t be shown again). We’ll use them in Step 5.

Step 3: Create a NetSuite role and add it to a user

  1. Still in NetSuite, navigate to Setup > Users/Roles > Manage Roles. Click New to create a new role.

  2. Give the new role a name, such as “ConductorOne integration”.

  3. Assign the following permissions to the role:

    • Setup - REST Web Services
    • Setup - Log in using Access Tokens
    • Setup - Bulk Manage Roles
    • Reports- Suite Analytics Workbook
    • Lists - Employee Record
    • Lists - Employees

    Why are these permissions needed? The integration uses these permissions to read and query SuiteQL tables containing information on roles and employees. The integration currently only reads data, it doesn’t write any changes.

  1. Click Save.

  2. Next, assign the new role to a user. You might want to create a new user for this purpose rather than assigning the role to an existing user. Navigate to Lists > Employees > Access.

  3. Click Roles. Select the newly created role and click Add.

Step 4: Generate a token key and token secret

  1. In NetSuite, navigate to Setup > Users/Roles > Access Tokens. Click New to create a new token.

  2. Select the application (integration), role, and user you created in the previous steps, and give the token a name.

  3. Click Save. The new token is created, and its key and secret are shown.

  4. Make a careful note of these credentials (they won’t be shown again). We’ll use them in Step 5.

Step 5: Add your NetSuite credentials to ConductorOne

  1. In ConductorOne, navigate to the NetSuite connector by either:

    • Clicking the Set up connector link in the email you received about configuring the connector.

    • Navigate to Connectors > NetSuite (if there is more than one NetSuite listed, click the one with your name listed as owner and the status Not connected).

  2. Find the Settings area of the page and click Edit.

  3. In the Account ID field, enter the domain you looked up in Step 1.

  4. In the Consumer key and Consumer secret fields, enter the credentials you generated in Step 2.

  5. In the Token key and Token secret fields, enter the credentials you generated in Step 4.

  6. Click Save.

  7. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your NetSuite connector is now pulling access data into ConductorOne.

Configure the NetSuite integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between NetSuite and ConductorOne.

See the ConductorOne NetSuite integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.