Description
Supplied retention-clock bookkeeping with a separate hold flag; no backup deletion occurs.
Security records often depend on explicit counts, clock origins, status flags, and provenance dates. Checking their internal arithmetic can reveal a bookkeeping gap while leaving the underlying evidence and operational decisions for separate review.
Supplied retention-clock bookkeeping with a separate hold flag; no backup deletion occurs.
When to use this tool
Use it for backup snapshot expiry slack when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter createdTime, retention, queryTime, legalHold. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read expiryTime, slack, expiryBlocked. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Compute expiryTime = createdTime+retention and slack = expiryTime-queryTime, and copy legalHold into the separate expiryBlocked flag. Retention must be nonnegative.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| createdTime | Created Time | Required. Finite number. |
| retention | Retention | Required. Finite number; minimum 0. |
| queryTime | Query Time | Required. Finite number. |
| legalHold | Legal Hold | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| expiryTime | Expiry Time | Required. Finite number. |
| slack | Slack | Required. Finite number. |
| expiryBlocked | Expiry Blocked | Required. Boolean. |
{
"input": {
"createdTime": 100,
"retention": 30,
"queryTime": 120,
"legalHold": false
},
"output": {
"expiryTime": 130,
"slack": 10,
"expiryBlocked": false
}
}Limitations and assumptions
- A hold does not change expiryTime or slack. The tool does not determine legal retention, inspect snapshots, perform deletion, or change a backup system.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For backup snapshot expiry slack, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Protective Asset Review Slack
Compare explicit protective asset record review times without security assessment.
- Advisory Publication Lag
Compare supplied public advisory timestamps without evaluating threats or recommending operational action.