Skip to main content
Each decision that PMG or the pull request check makes with the cloud policy carries a citation: the policy revision, the revision of the SafeDep default policy, and the package rule or the setting that decided. Use the citation to answer “why was this package blocked?” for one endpoint or one pull request.
This guide needs the SafeDep Cloud Team or Enterprise plan. See pricing. A user with the ReadOnly role or a higher role can read the decision log.

Read the citation where the decision happened

In PMG. A block entry of the cloud policy stops the install with a message that names the rule. This example comes from the PMG tests:
In a pull request check. A failing check shows a policy block with the revision, the settings and the rule of each finding. See What the check shows.

Show the rule

The output shows the selector, the effect, the scopes, the reason, the ticket, the requester, where the rule attaches, its expiry, its author, and the revisions that added and removed it.

List the decisions

safedep policy decision list lists the decisions of the tenant, newest first. Each row names the tool, the package, the outcome, the rule or the setting that decided, the revision and the place of the decision. The decisions of one package rule:
The installs that the cloud cooldown blocked in the last day:
The decisions about one package, in all its versions, on one endpoint:
Other filters: The --package filter takes a PURL with no version. The name must match the stored name exactly, with the same case.

What is not in the decision log

  • A decision with no citation: a block by the malware analysis alone, a block by the PMG blocked_packages list, and a cooldown block when the cooldown came from the PMG config and not from the cloud policy.
  • A PMG decision that PMG did not sync yet. PMG syncs its events to SafeDep Cloud with cloud.enabled on. See Package Guard.

Show the policy of one subject

To see the value of each setting for one endpoint or project, and the layer that set it:
The output also shows the revision that each tool applied, and the exceptions that it reported, such as a field that a managed config file locks.

Next steps

Policy Resolution

Layers, policy overrides and the resolved policy.

Trust a Package

Act on a block that was wrong.

Command Reference

Every flag of safedep policy decision list.