Optional infrastructure and privacy value

Use these optional buckets only when they clearly apply and can be supported with reasonable assumptions.

Optional: lower infrastructure cost

Include this only when non-production infrastructure savings are clearly in scope.

Do not double-count the same infrastructure savings in both the copies-retired and TB-reduction methods.

Model infrastructure savings by the number of non-production copies retired or avoided.

Number of non-production copies retired or avoided.

K2view default
Med

Fully loaded annual cost of one non-production copy (storage, database, environment).

K2view default
Med
USD

Model infrastructure savings by terabytes of non-production data reduced.

Terabytes of non-production data reduced.

K2view default
Med

Annual cost per terabyte of non-production storage.

K2view default
Med
USD

Optional: lower privacy risk exposure

Include this only when privacy, security, or compliance risk reduction is part of the business case.

Use privacy-risk value only when privacy, security, or compliance risk reduction is part of the business case. Keep assumptions conservative and avoid broad breach-cost claims.

Model privacy value from a reasonable maximum fine or penalty exposure and a conservative probability reduction.

Reasonable upper bound of privacy fine or penalty exposure.

K2view default
Med
USD

Reduction in the probability of incurring that fine or penalty, in percentage points. Keep conservative.

K2view default
Med
%

Model privacy value from an estimated annual privacy-related loss and the share K2view masking can reduce.

Reasonable annual privacy-related loss estimate.

K2view default
Med
USD

Expected reduction in that loss from K2view data masking, in percentage points. Keep conservative.

K2view default
Med
%