Features and Capabilities
Learn the core JFrog Curation features for package governance.
JFrog Curation includes several core features to enforce security, compliance, and operational control:
Policy-Driven Package Governance
Curation policies enforce security, licensing, and operational rules on package downloads. Curation evaluates policies at the repository level to ensure compliance.
Policies are based on different conditions, custom and predefined. A policy can use one of the following actions:
- A blocking policy blocks the developer from using the package that violated the policy.
- A dry-run policy assesses impact on the organization before it becomes a blocking policy.
Conditions, Custom Conditions, and Condition Templates
- Predefined Conditions: Out-of-the-box rules provided by JFrog to address common security, operational, and legal risks, for example blocking malicious packages, outdated versions, end-of-life packages, or licenses.
- Custom Conditions: Templates allow administrators to create tailored conditions. These allow organizations to address specific needs, such as blocking packages vulnerable to a specific CVE or requiring certain operational thresholds.
- Advanced Condition Settings: Some templates support more advanced configurations that create a relaxed condition. Relaxed conditions can decrease the false-positive impact of broad policies and block only packages that answer multiple parameters.
- Usage of Conditions in Policies:
- Each policy contains a single condition that defines its enforcement criteria.
- Custom conditions provide granularity and adaptability for unique organizational requirements.
- Conditions are pivotal to determining which packages are approved or blocked during evaluations.
Waivers
Waivers exclude specific packages or versions from policy restrictions. You can apply them through JFrog Catalog labels or manual configuration.
You can apply waivers in the following ways:
- A package version is applied directly to the policy.
- Catalog labels are used to mark the desired package versions, and then the label is attached to one or more policies. If you want waivers for a broader set of packages, this approach supports bulk actions and reuse of labels on other policies.
Compliant Version Selection
When a requested package version is blocked by a curation policy, Compliant Version Selection automatically returns the highest version that passes all policies instead of failing the request. This ensures developers can continue working without disruption, while still enforcing security and compliance rules.
- Automatic Fallback: When a blocked version is detected, Curation evaluates all available versions within the dependency range and returns the highest compliant one. This covers both direct and transitive dependencies.
- Seamless Developer Experience: Developers aren't notified when a different version is delivered. Builds succeed transparently with a compliant version.
- Supported Package Types:
- Full Support: npm, PyPI, Maven, Go, NuGet, Gems, and Conda.
For more information, see Fallback Behavior for Blocked Packages.
Curation Federation
Organizations that operate the JFrog Platform at multiple sites can use Curation Federation to synchronize curation rules across all sites from a single central location.
- Controller and Followers: One site is designated as the controller, and it's the source of truth. All connected sites act as followers and automatically receive policies, conditions, and JFrog Catalog labels.
- Policy-Level Sharing: Not all policies are federated by default. Administrators opt in to individual policies by enabling Share with Federation in the policy settings. Only policies with scope All Curated or Package Types can be shared.
- Federated Entities: Curation synchronizes a few types of entities: package-type connection settings, custom conditions, Catalog labels, and shared policies.
- Local Flexibility on Followers: Follower sites can customize federated policies for local needs. They can adjust excluded repositories, notification emails, decision owners, and waivers without changing the centrally managed rule.
- Asynchronous Synchronization: Federation propagates updates in near real time using asynchronous federation services. If a follower becomes temporarily disconnected, it may lag behind until connectivity is restored. You can trigger a full sync to reconcile any missed updates and ensure consistency.
For more information, see Curation Federation.
On-Demand Curation
On-Demand Curation extends JFrog Curation to secure packages from remote repositories that aren't covered by the JFrog Public Catalog. Those repositories include internal, private, and ecosystem-specific repositories whose packages haven't been cataloged yet.
- Real-Time Policy Enforcement: When a developer requests a package from an uncataloged repository, Curation intercepts the request and applies your organization's existing policies. Curation evaluates vulnerabilities, licenses, malicious code, and immaturity before releasing the package.
- On-Demand Catalog: Curation stores results in a dedicated On-Demand Catalog, separate from the Public Catalog. You can access them through the UI and API. Future requests for the same package are instantaneous.
- Seamless Activation: On-Demand Curation builds on the Block-from-Cache mechanism. Once enabled, you can activate it per package type or per individual repository.
- Consistent Governance: The same policy types that apply to Public Catalog packages also apply to on-demand packages. Those types are vulnerabilities, licenses, malicious packages, and immaturity. Labels and waivers are fully supported.
- Docker Support: On-demand scanning is available for Docker containers and images, with vulnerability and license insights visible in the Docker UI.
- UI Indicators: On-demand packages are clearly marked with an On-Demand tag in search results, repository lists, and package detail pages. The See All page shows Public Catalog and On-Demand Catalog results in separate tabs.
For more information, see On-Demand Curation.
Audit and Reporting
Audit is a crucial function of Curation. Every package inspected in Curation has an audit event log. If a policy relaxation condition blocks or bypasses the package, the event log records it.
You can use audit for the following:
- Viewing blocked and approved package events.
- Running dry-run evaluations to simulate policy enforcement without blocking downloads.
- Accessing detailed audit logs for compliance and troubleshooting.
Curation User Audit: Any user action in Curation is logged for regulations and documentation.
Integration with JFrog CLI
Developers can use the JFrog CLI for the following:
- Checking curation violations for a project.
- Viewing detailed policy decisions for specific packages.
Curation-Catalog Integration
- The JFrog Catalog serves as a metadata repository for package evaluation, enabling the Curation service to assess and block or approve packages in real time.
- Dynamic metadata updates ensure Curation evaluates packages against the latest security and licensing data.
- Organizations can manage both public and private metadata through JFrog Catalog for tailored curation capabilities.
- Labels in the JFrog Catalog group and manage packages based on organizational requirements. These labels can be applied to:
- Allowlists: Accept only pre-verified packages for use.
- Blocklists: Block specific packages or versions at scale.
- Waivers: Exclude labeled packages from curation restrictions.
Operational Statistics
Curation has minimal performance impact, with average evaluation times of about 100 milliseconds per package request.
Related Topics
Updated about 1 month ago
