Description
Require notifiedTimestampSeconds no earlier than eventTimestampSeconds and return their difference.
Security administration uses retention periods, control owners, acknowledgments, recovery targets, and test records. Arithmetic and labels can make these records consistent, but they do not demonstrate that a control works or that a policy is adequate.
Require notifiedTimestampSeconds no earlier than eventTimestampSeconds and return their difference.
When to use this tool
Use Humanitarian Notification Delay when you need a narrow security-record calculation or formatter under supplied policy values.
How to use the tool and how it works
- Enter eventTimestampSeconds, notifiedTimestampSeconds. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read delaySeconds. Use the output convention below.
Require notifiedTimestampSeconds no earlier than eventTimestampSeconds and return their difference.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| eventTimestampSeconds | Event Timestamp Seconds | Required. Finite number. |
| notifiedTimestampSeconds | Notified Timestamp Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| delaySeconds | Delay Seconds | Required. Finite number. |
{
"input": {
"eventTimestampSeconds": 1000,
"notifiedTimestampSeconds": 1120
},
"output": {
"delaySeconds": 120
}
}Limitations and assumptions
- Clocks must be compatible and synchronized; notification timeliness, emergency adequacy, and incident authenticity are not judged.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Review the complete control evidence, applicable policy, and operational tests before making a security decision.
References
Similar or alternative tools
- Message Ack Delay Pair
Require acknowledgedTimeSeconds no earlier than sentTimeSeconds and subtract for delaySeconds.
- Case Handoff Receipt Delay
Require receivedTimestampSeconds no earlier than sentTimestampSeconds and return their difference.