endor-validate-policy

You can validate an Endor Labs exception policy by using the PolicyValidation API or endorctl parity workflows to check if stored policy rules match specific project findings or finding UUIDs without applying production changes. This requires tenant namespace alignment and policy identifiers.

Endor Labs policy validation returns 403 errors due to tenant namespace misalignment. You must ensure your authorization context matches the namespace where the target policy and project findings are stored before executing validation requests or parity workflows.

SDK and endorctl policy validation differ in request shape, authentication methods, and result formatting. You can compare both validation outputs using parity workflows to understand behavioral differences before committing to a specific automation approach.

Yes, you can run preview-only syntax validation for Endor Labs policy templates. This checks template value structures, including VulnID matching and MatchApproximate behavior, without fully evaluating the policy against loaded project findings.

To troubleshoot VulnID matching issues in Endor Labs exception policies, validate the stored policy template values against specific finding UUIDs. This isolates MatchApproximate behavior and template value mapping problems without modifying active production rules.