Part 2: Prepare for Curation Rollout
Prepare roles, access, and settings before you roll out Curation.
Install Curation for Self-Managed Customers
Before getting started, make sure you've installed JFrog Xray and JFrog Catalog. Installation guidance covers the following services:
- JFrog Xray
- JFrog Catalog
Curation Permissions and Roles
To separate responsibilities and permissions on the JFrog Platform, Curation supports the same roles as JFrog Xray for the following responsibilities.
- Administer Platform: System administrators or DevOps engineers typically use this role. They configure and maintain Curation, manage repositories, and oversee policies.
- Manage Policies: Security teams or compliance managers typically use this role. They create and manage policies, as well as monitor Curation coverage and usage statistics to ensure adherence to organizational standards.
- Read Policies: Developers or project managers typically use this role. They can view policies and Curation coverage. They can't change settings or conditions.
You can use these roles to oversee and govern Curation.
For a detailed description of these roles and where to set them up, see Set User Roles and Permissions.
Enable Curation Product
Starting Curation requires three steps.
To enable Curation:
- Activate the service
- Connect package types or single repositories
- Create policies to protect your organization
To open Curation settings:
- In the Platform UI, go to Administration Tab > Curation Settings.
This is how it should look at the end of the process:
Package Pending Update Settings
When you configure Curation package settings, Catalog sometimes can't find a package.
Note
It can take up to 4 hours for Catalog to update its database and return an answer the next time the package is downloaded.
You can choose one of the following options for packages that aren't found.
- Allow if No Blocking Policy on Remote:
- Description: This setting permits access to a package only if no blocking policies exist for remote repositories.
- Implication: This option keeps some security in place and still allows flexibility for packages that were not previously identified as risky.
- Block Always:
- Description: This setting blocks any package that Catalog can't find, whether or not policies already exist.
- Implication: You prevent access to unverified packages. This can slow development.
- Allow Always (Not Recommended):
- Description: This setting allows every package, even when Catalog can't find it or the package is unverified.
- Implication: You get the most flexibility, and you also take on significant security risks. When you test Curation, set Allow if No Blocking Policy on Remote.
Notify on Package Blocked Event
This setting sends notifications whenever a package download is blocked due to policy violations or other issues.
- Email Package Requester: The person who requested the package receives an email that explains the block and the reason.
- Email Others: Additional stakeholders or team members receive an email about the blocked package, so more of the team is aware.
When to Move On
Once you finish preparation, you're ready to begin hands-on enforcement with minimal risk.
Proceed to Part 3: Block Malicious Packages
Related Topics
Updated 14 days ago
