Description
Require responseTimestampSeconds ≥ signalTimestampSeconds and return their difference as delaySeconds.
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 responseTimestampSeconds ≥ signalTimestampSeconds and return their difference as delaySeconds.
When to use this tool
Use Protective Drill Response 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 signalTimestampSeconds, responseTimestampSeconds. 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 responseTimestampSeconds ≥ signalTimestampSeconds and return their difference as delaySeconds.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| signalTimestampSeconds | Signal Timestamp Seconds | Required. Finite number. |
| responseTimestampSeconds | Response Timestamp Seconds | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| delaySeconds | Delay Seconds | Required. Finite number. |
{
"input": {
"signalTimestampSeconds": 100,
"responseTimestampSeconds": 112
},
"output": {
"delaySeconds": 12
}
}Limitations and assumptions
- Use synchronized clocks; this records one drill delay without assessing response adequacy, readiness, or real emergency outcomes.
- 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
- Humanitarian Notification Delay
Require notifiedTimestampSeconds no earlier than eventTimestampSeconds and return their difference.
- Message Ack Delay Pair
Require acknowledgedTimeSeconds no earlier than sentTimeSeconds and subtract for delaySeconds.