ASOM-Fedv6.1Open the explorer
TA-5 · Tempo and Temporal Advantage

Tempo Degradation Trigger

Control Statement

Conditions under which the defender decision loop is expected to degrade shall be identified, with compensating measures defined.

Purpose. To plan for the periods in which tempo predictably falls, so that the measured advantage is not a statement about the organization's best hours only.

Discussion

Tempo is not a constant, and its degradation is not random. Nights, weekends, federal holidays, shift handovers, key-person absence, hiring gaps, contract transitions and major change windows all reduce the loop — and adversaries select those windows deliberately. A temporal advantage figure computed across a cycle averages over these conditions and therefore overstates the position at exactly the moments contact is most likely. This control exists so the average is not mistaken for the floor.

Goals and Metrics

A metric that cannot come out badly is not a metric. Each of these is capable of reporting that the control is not working.

Degradation conditions are identified with compensating measures.
  • Number of identified degradation conditions with a defined compensating measure
  • Measured loop time during a degradation event versus baseline

Accountability

Exactly one role is accountable, and every other role carries at least Informed — no control in the published catalog leaves a role with zero relationship to it. That is a stated property of how these were authored, not a coincidence, and not a claim that every role's work is worth equal attention here.

AOCTISOCHUNTPLATISSO
Authorizing Official / CISO: AccountableCyber Threat Intelligence cell: InformedSOC / Defensive Operations: ResponsibleHunt team: InformedPlatform and product owners: ConsultedGovernance / RMF / ISSO: Consulted

AO Authorizing Official / CISOCTI Cyber Threat Intelligence cellSOC SOC / Defensive OperationsHUNT Hunt teamPLAT Platform and product ownersISSO Governance / RMF / ISSO

  • AccountableAuthorizing Official / CISO
  • InformedCyber Threat Intelligence cell
  • ResponsibleSOC / Defensive Operations
  • InformedHunt team
  • ConsultedPlatform and product owners
  • ConsultedGovernance / RMF / ISSO

Inputs and Outputs

Consumes

Produces

Activities

  1. L2Identify the conditions under which the decision loop is expected to degrade.
  2. L2Define a compensating measure for each condition.
  3. L2Record both alongside the tempo measurement.
  4. L3Include organizational conditions as well as operational ones — contract transition, key-person absence, hiring gaps and handover windows, not only nights and weekends.
  5. L3Estimate the expected degradation per condition, so compensation can be sized rather than gestured at.
  6. L3Assign an owner to each compensating measure and confirm it is available during the condition it compensates for.
  7. L3Report tempo at the degraded condition as well as in aggregate, so the floor is visible next to the average.
  8. L4Measure actual loop performance during degraded conditions against the estimate, and correct the estimate where it was optimistic.
  9. L4Correlate incident timing against degraded windows, since adversary selection of those windows is itself a measurable finding.
  10. L5Redesign staffing, automation or authority scope to remove the degradation condition rather than compensating for it indefinitely.

Measurement

Outcome

Measured loop performance during degraded conditions against the aggregate figure.

Performance

Percentage of identified conditions with an owned, available compensating measure.

Evidence and Assessment

Evidence expected

Degradation register with compensating measures and owners; degraded-condition tempo figures; incident-timing correlation.

Assessment procedure

Examine the register; interview operations on a recent period of degraded capacity; test whether the compensating measure was in fact available during it.

Related Guidance

Inherits
  • IR-4
  • CP-2
  • PS-2
Satisfies
  • RS.MA-01
  • ID.IM-01

Position in the Chain

Derived from the other controls’ own declarations, so the two directions cannot disagree.

Feeds

Nothing downstream — this control terminates a chain.

Where This Control Is Used

Derived, in every case, from the declaration at the other end: the forms whose techniques name this control, the artifacts whose producing and consuming controls include it, the layers whose control lists name it, and the roles its own accountability chart puts to work. Nothing here is authored on this page, so the sheet cannot claim an edge the other end does not.

Forms of Maneuver It Assesses

  • M6DelayBuy decision time and prevent the adversary culminating on the objective.6 of 10 techniques — M6.01, M6.03, M6.06, M6.07, M6.08, M6.09
  • M8Isolation / RetrogradeGive ground deliberately to preserve the force. Degrade gracefully; never fail open.1 of 17 techniques — M8.03

Terrain It Is Named On

  • T7WorkforceThe tempo degradation trigger is the control that detects the culminating point — the defending force’s own saturation.

Artifacts It Stands On

  • producesTemporal advantage resultDefender decision loop against adversary dwell, reported as a ratio against the threshold set at Frame, with the result written as a word: met, or not met. The framework’s single honest scoreboard.
  • consumesBarrier sufficiency registerThe specific barriers holding the line where reachability is prevented, each with a named enforcing owner. What the reachability result depends on, made explicit so its erosion is visible.
  • consumesDefender decision loop measurementDetect to decide to contain, measured per incident from the change record’s timestamps and reported as a distribution rather than as a mean.
  • consumesRole-based readiness recordPreparation targeted at the tradecraft that actually targets each role, and the gaps that would slow the decision loop if the role were needed under contact.

Roles It Puts to Work