Business Critical accounts not using any edition-gated features

The $1-per-credit question

Every Snowflake invoice is credits multiplied by a per-credit rate, and the rate is set by edition. At list pricing, an account on Business Critical pays about $1 more per credit than the same account would on Enterprise. An account consuming 2,000 credits a month is therefore paying roughly $2,000 every month for the Business Critical feature set. If Tri-Secret Secure or the compliance posture is in active use, the premium is the point. If nothing edition-gated is in use, the premium buys nothing.

What the discoverer actually reads

Two attributes stamped on the account resource by ZopNight’s discoverer: edition, which must be BUSINESS_CRITICAL or VPS, and a gated_features_used flag, which must be "false". The signal itself is just a presence check. The applies-to gate does all the filtering. Confidence is deliberately set to 0.5, the lowest of the Snowflake rules, because feature-use probing cannot see everything: seasonal workloads, features exercised only in disaster-recovery drills, or usage buried in procedures can all look like “unused” in a snapshot. The probe list follows the upstream rule definition: masking policies, external functions, Tri-Secret Secure and similar edition-gated capabilities.

Take your own inventory of gated features

A quick pass over the policy views shows whether anything gated is live:

SELECT 'masking_policies' AS feature, COUNT(*) AS in_use
FROM SNOWFLAKE.ACCOUNT_USAGE.MASKING_POLICIES
WHERE deleted IS NULL
UNION ALL
SELECT 'row_access_policies', COUNT(*)
FROM SNOWFLAKE.ACCOUNT_USAGE.ROW_ACCESS_POLICIES
WHERE deleted IS NULL;

Zero rows of live policies, no external functions, and no Tri-Secret configuration is the picture that matches this finding. ACCOUNT_USAGE views lag by up to a few hours, so a policy created this morning may not appear yet.

Why this finding never acts on its own

Edition is not a knob ZopNight will ever turn. Downgrading is a contractual change that goes through your Snowflake representative, and Business Critical is frequently mandated by regulators or customer contracts rather than chosen for features. HIPAA and PCI commitments are the usual reasons. The recommendation is strictly advisory: it exists to put the per-credit premium in front of the person who can confirm whether the compliance obligation still stands. Treat the finding as an agenda item for that conversation, not a change ticket. If compliance sign-off confirms the edition is required, dismiss the finding and it will not nag; the flag only means the technical evidence for the premium was not found.