This guide needs the SafeDep Cloud Team or Enterprise plan and the Admin role. See pricing.
Create the trust entry
- The selector names one package. Add a version in the PURL, or a range with
--vers, to trust only some versions. A trust entry cannot use a prefix. --scopenames the verdicts to waive. Give it more than once, or useall. See Choose the scope.--expiresis required. It takes a duration, as30d, or a date, as2027-01-26. The expiry is at most 90 days from now.--reasonis required.
Choose the scope
Choose the narrowest scope.
--scope all expands to the scopes that exist now. A scope that a later release adds does not apply to this rule.
A trust entry never waives a verdict of verified malware, whatever its scope. A trust entry also never skips the malware analysis. If a block entry selects the same package, the block entry wins.
Extend or end the trust
To extend the trust entry, give a new expiry. A later expiry loosens the policy:Move from Malicious Package Exclusions
Trust entries with the scopemalware replace Malicious Package Exclusions. SafeDep Cloud does not copy exclusions into the cloud policy. For each exclusion that you still need, create a trust entry:
PMG with
cloud.policy on ignores the exclusions and applies only the trust entries.
Next steps
Package Rules
Trust scopes and the verified malware guard.
Explain a Decision
List the installs that a trust entry allowed.
Malicious Package
How SafeDep classifies a package as malicious.
Command Reference
Every flag of
safedep policy rule.
