Custom Policy Source
Last updated
Was this helpful?
Last updated
Was this helpful?
Custom policy source refers to a mechanism or source from which CI systems can retrieve and apply custom policies or rules to the code being built or integrated. These policies or rules could be related to coding standards, security checks, compliance requirements, or any other guidelines that the development team wants to enforce as part of the process.
Users can import existing security policies from their organization or create new policies using the custom policy source.
Delivery Shield will periodically scan the custom policy repository to detect and import any changes. For more information, see Custom Policies.
Navigate to Setup > Integrations.
In the Others panel, click Custom Policy Source.
You can use the toggle button provided below the integration tile to enable or disable it as needed.
The Custom Policy Source integration page is displayed. Click +New Account.
In the popup that appears, enter the following details:
Enter the Account Name, Repo URL & Path and Token.
Select the Teams and the corresponding Environments from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only.
You can select up to 5 teams for the integration to be displayed.
A sample is given below for reference:
In the example above,
if Team 1, Team 2, and Team 3 are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as Team 4, will not have access to this account.
Even if the user who created this account is also an admin for Team 4, the integration account remains restricted and is not available for Team 4.
Access to the account is strictly limited to the specified Teams and Environments selected during account creation.
For Organization Admins:
When an Organization Admin creates an account without selecting specific Teams and Environments, the account will be universally applicable, granting access to all teams and all environments by default.
For Team Admins with Multiple Teams:
If a Team Admin who manages multiple teams creates an account without specifying particular Teams and Environments, the account will only be accessible to the teams for which the logged-in user holds admin privileges.
Click Save. The tool is connected.
You can edit the entered values by clicking the Edit option as shown below:
Re-enter the values and click Update.
The new values gets updated.
