As explained in the Introduction of this guide, you can choose to onboard an AWS standalone application when your AWS organization has only independent AWS accounts and does not have a management AWS account. The following diagram shows the basic

resources_generator : The bootstrap script to execute to dynamically generate/get the resources the broker will support when registering the agent via the broker bootstrap endpoint. For more information about configuring the resource generator script, see Creating Resources . http

GA Release 2022.02.02 GA Release 2022.02.01 GA Release 2022.02.02 What's New  Support for Snowflake (Standalone & Org) as JIT connector. For more information, see Snowflake Onboarding Guide . Improvements GCP apps - Collect specific folders/projects

A custom role needs to be created for Britive to perform operations within GCP. To scan all folders and projects in an organization, create a role with the configuration shown in Create Custom role for GCP organization . To scan a

An administrator creates a vault for every respective tenant to store and manage secrets. A vault is a container holding secrets and nodes. A node is a directory or a folder holding secrets. Each secret is encrypted using a tenant

As a best practice, Britive suggests granting access to Britive profiles via groups. For more information, see Group Sync with SCIM . Configuring an Identity Provider on Britive An identity provider needs to be created in Britive for SSO. Log in

Britive administrators can set a global session timeout for all users, including those authenticated through external identity providers and local Britive accounts. This standardizes session management for all user types. Log in to Britive as an administrator. Click on Admin

You can view the details of the onboarded Oracle application from Britive such as scans, related graphs and charts, profiles, or properties. You can also make necessary edits, or perform scans or profile checkouts if needed. Details of the Onboarded

A custom role needs to be created for Britive to perform operations within GCP. The custom role can be created at one of the following locations:  Organization level:  In this scenario custom role can be created at the organization level

You need to create and configure an incident management connection with Pagerduty in Britive. Britive needs the following Pagerduty parameter for configuration: API Token of Pagerduty account Creating Incident Management Connection in Britive Log in to Britive. Click on Admin

Datadog is a SaaS based monitoring and analytics platform for large-scale applications and infrastructure. To know more about Datadog, see the Datadog documentation . Britive can deliver audit logs to Datadog via a webhook. Custom Log Intake Endpoint on Datadog

The onboarding prerequisites include getting the required accounts and access and performing specific configurations in GCP, as explained in the following sections. Britive needs a service account that provides access to GCP to read roles, users, and IAM policies. After

Profiles define what actions an identity can perform on a resource. Profiles have profile details, associations with resource label conditions, permissions for resources, and policies. Users who have Manage permission for the resource can create profiles. Creating an Access Profile

Britive authorization allows granular and flexible access, permissions, and policies. With this policy-based access control, the user can add/create new roles and permissions to have customized policies as per the requirements and operational processes. Britive comes with the

GA Release 2025.11.01 GA Release 2025.10.01 GA Release 2025.11.01 Released on 16 th November, 2025. What's New Support for AI identities. For more details/information, see AI Identities . Improvement Grant ownership of users

Before creating a service account, make sure you have enabled the cloud APIs. For more details, see Enabling Cloud APIs . Login to GCP Console using administrative privileges. Select IAM & Admin -> Service Accounts from the navigation menu. Select the project where

GA Release 2023.07.01 GA Release 2023.06.02.01 GA Release 2023.07.01 Released on July 30 th , 2023. Fix An issue with group name parsing is fixed for the Okta application. GA Release 2023.06.02

Once you have onboarded the GCP application to Britive, you can scan the organizations and environments. The scans that are submitted are visible in the Scans tab of the onboarded GCP application. Steps for Scanning the GCP application Perform the

This document describes the steps required to configure Salesforce Connector. Britive needs a custom user and permission_set with privileges to perform scan and Just-In-Time (JIT) provisioning of access. Britive needs the following to onboard a Salesforce application

Before onboarding the AWS Identity Center application to Britive, you need to add Britive as the Identity Provider in the AWS account and also create IAM role(s) in the account. Configuring Britive Identity Provider in AWS Configuring IAM Roles