Britive now extends the MFA for user authentication. Users can now register and log in using MFA. Logging for First-time Users The administrator has created a user with initial credentials (username/password) and has already configured allowed MFA settings

Once you have onboarded the AWS application to Britive, use the Scan button in the Settings tab to start a new scan. You can perform an organization scan(s) or environment scan(s). The organization scan in Britive is applicable

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

A notification medium is used to send notifications when secrets need to be rotated or to send approval requests. While email and email with magic links are the default notification mediums, you can also use other mediums such as Slack

Britive datasets are shipped in two formats: History( ): A daily snapshot of the data taken at the end of the day Latest ( ): The most recent snapshot Britive provides the following out-of-the-box physical datasets: Dataset Name Description access

GA Release 2022.06.02.02 GA Release 2022.06.01 GA Release 2022.06.02.02 Released on July 10 th , 2022. Improvements Diagnostics tile has been renamed as Audit Log on the Admin landing page. Users can now

This guide provides the details about the Britive application and Okta provisioning integration. Supported Features Requirements SCIM Configuration Steps Known issues Supported Features Push New Users New users created through Okta will also be created in Britive. Push Groups Groups

GA Release 2023.02.02 GA Release 2023.02.01.02 GA Release 2023.02.02 Released on March 5 th , 2023. What's New Released a new Python SDK and command line interface ( P yBritive ) designed to better integrate

GA Release 2023.09.01.01 GA Release 2023.08.02.01 GA Release 2023.09.01.01 Released on September 24 th , 2023. Improvements Profile checkout duration can now be configured for up to 7 days for all applications

This guide provides details about Britive and CyberArk Identity SSO integration. Configuration Steps Configuring an Identity Provider on Britive An identity provider needs to be created in Britive for SSO. Log in to the Britive application with administrator privileges. Click

An Identity Provider helps to manage your user identities outside of AWS, by granting permissions to the user identities to utilize the AWS resources in your account. In the AWS onboarding process, the Britive application (tenant) is added as the

This onboarding guide explains how to onboard Google Cloud Platform (GCP) Workload Identity Federation (WIF) applications to Britive. Once you have registered Britive as an application in GCP and configured the prerequisite steps, you can proceed with the onboarding steps

Login to Britive. Click on Admin -> Role & Policy Management -> Policies . The list of policies is displayed. The following actions are available for the policies: Manage policy : You can Edit, Clone, Disable, or Delete a policy. Enable/Disable policy : You can

Many organizations use IT Service Management (ITSM) systems like Jira Service Management or ServiceNow to track incidents or application changes. Britive extends its functionality to allow customers to connect to their ITSM system and carry out incident—or change-related

This guide describes step-by-step instructions for integrating Britive with an identity provider. The identity provider is used for single sign-on (SSO) and/or provisioning users and groups.  SSO uses the Security Assertion Markup Language (SAML 2.0

The following prerequisites are required on the AWS side to enable Session Invalidation feature: Each Integration Role in the AWS environment must be updated to allow the following additional API actions: { "Version": "2012-10-17", "Statement": [ { "Action": [ "iam:CreatePolicy", "iam

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

The prerequisites for dynamic permissioning include: Registering Britive Application in Microsoft Entra ID Generating Client Secret Assigning Azure Permissions for Dynamic Permissioning Assigning Directory Permissions for Dynamic Permissioning In the above prerequisites, 1 and 2 are common prerequisites explained earlier

Britive offers a wide range of out-of-the-box tenant application integrations, including AWS, GCP, Salesforce, and more, to streamline onboarding. However, some organizations may need to integrate with in-house or custom applications. To meet this need, Britive

You must enable the APIs required for Britive to read user, role, and group information from the GCP. The APIs should be enabled on the project where the service account is going to be created. Login to GCP Console with