ASOM-Fedv6.1Open the explorer
Reference manual · glossary

The Vocabulary, and What It Is Not.

ASOM-Fed borrows its language from land-warfare doctrine, and borrowed words are the framework’s largest failure mode. A reader who takes “key terrain” to mean “important system”, or “main effort” to mean “top of the priority list”, will produce artifacts that look correct and decide nothing — because the distinctions those words carry are the entire reason they were borrowed.

38TermsEach with an origin and a working definition
38With a named impostorThe term most often mistaken for it
39Controls citedWhere the term is operationalised
12Letters in useAlphabetical, no sub-classification
How to Read an Entry

Origin, Meaning, and the Term It Gets Mistaken For.

The third part is the one that earns the page. Most misuse of this vocabulary is not ignorance of the term; it is confident substitution of a near neighbor that behaves differently.

This page defines the terms used inside the framework’s object classes. To tell the classes themselves apart — a tower from a terrain layer, a tier from either — the object model does the same three-part job for all ten.

Doctrinal origin

Where the term comes from, stated in its original sense. Kept because the original usually carries a constraint the cyber translation tends to drop — an obstacle that is not observed, for instance, does not impede for long.

On a federal network

What the term means here, concretely enough to act on, with the controls that operationalise it named.

Not to be confused with

The near neighbor, and what actually differs. Omitted where a term genuinely has no impostor — padding this field would make the useful ones harder to find.

Where it is used

Controls and pages that put the term to work. Control links resolve against the real catalog, so a term cannot cite a control that does not exist.

A

Avenue of approach

Doctrinal origin

Terrain analysis. An avenue of approach is a route by which a force can reach an objective — assessed for the size of force it supports, the cover it offers, and where it can be observed or blocked.

On a federal network

A path an adversary can actually traverse from a starting position to a decisive point, across the permitted connections the estate really has. In ASOM-Fed an avenue is traced over the connection register (TM-5) rather than imagined: it begins at a declared threat-actor position, crosses named zone boundaries, and ends at a designated decisive point. Indirect routes through intermediate systems count, and usually dominate — adversaries rarely arrive on the direct edge.

Not to be confused with

An attack surface. A surface is everything exposed; an avenue is a specific traversable route to a specific objective. Enumerating surface produces a large number nobody can act on; enumerating avenues produces a small list you can site defensive moves on.

Where it is used

B

Barrier

Doctrinal origin

Obstacle doctrine. A barrier is an obstacle or a group of obstacles emplaced to stop or turn a force, distinguished from lesser obstacles by the fact that the plan depends on it holding.

On a federal network

The specific denied path that is preventing an adversary position from reaching a decisive point. Barriers are derived, not chosen: the reachability assessment (KT-4) identifies which denied paths are holding the line, and those become the load-bearing set. Each must be technically enforced rather than procedurally asserted, must have a named owner, and must be monitored — because a barrier that is removed during a change window fails silently and the reachability answer changes with nobody noticing.

Not to be confused with

A control. Most controls are not barriers. A barrier is the small subset whose removal would immediately change the answer to “can they reach it”, which is why they are inventoried separately and alerted on as security events rather than as routine changes.

Where it is used

Bill of Defense

Doctrinal origin

Not doctrinal. Borrowed from cost-transparency practice, where a consuming business unit receives an itemised statement of the services it consumes and what they cost.

On a federal network

The per-mission statement produced by the Defense Tower Model: for one mission service, the assets, defensive towers and maneuvers protecting it, its rolled-up coverage percentage, and the residual risk that remains. It is the artifact that lets a mission owner see defense the way a budget holder sees spend — attributable, traceable in both directions, and arguable.

Not to be confused with

A system security plan. A system security plan describes controls implemented on a system; a Bill of Defense attributes coverage upward to the mission that consumes it, and reports what is left over.

Where it is used

Branch

Doctrinal origin

Operational planning. A branch is a pre-planned option built into the current operation — a change of course taken during execution, in response to something that may happen.

On a federal network

A contingency maneuver planned before the cycle begins, with its trigger stated: if account takeover on external identities is confirmed, execute the envelopment maneuver on the identity plane. The value is entirely in the pre-planning — a branch decided at the moment of contact is not a branch, it is an improvisation, and it will be made by whoever is awake.

Not to be confused with

A sequel. A branch changes the current operation; a sequel is what you do after this one ends. Both are pre-planned; they differ in when they apply.

Where it is used

C

Canalization

Doctrinal origin

Maneuver. To canalize is to restrict a force to a narrow route where its movement is predictable and it can be engaged on ground of your choosing.

On a federal network

Deliberately shaping the estate so that lateral movement, when it happens, happens in instrumented segments. Microsegmentation, egress control and allow-listing are the mechanism; the intent is not to make movement impossible but to make it occur where you are watching. The measure is not “attempts blocked” but “attempts observed in instrumented terrain”.

Not to be confused with

Blocking. Blocking removes a path; canalization leaves a path open on purpose because a monitored path is more useful than a closed one you cannot see.

Where it is used

Commander’s intent

Doctrinal origin

Mission command. A concise statement of purpose, end state and acceptable risk, written so that subordinates can act coherently when the plan no longer fits the situation.

On a federal network

The defensive intent paragraph: what is being protected, what degradation is acceptable, and what must never happen — issued by the Authorizing Official, in one paragraph, in language a platform owner can act on without translation. “Protect mission-transaction integrity and sensitive mission records; degrade gracefully, never fail open” is intent. It is what allows a SOC to make a containment decision at 03:00 that the Authorizing Official would have made.

Not to be confused with

A policy statement or a mission statement. Policy constrains behavior in advance; intent enables decision in the absence of instruction. A statement that cannot be used to choose between two options under time pressure is not intent.

Confidence level

Doctrinal origin

Intelligence analysis (ATP 2-33.4). An explicit statement of how much weight an assessment can bear, published with the assessment rather than left to the reader.

On a federal network

An attached judgment about the evidence behind a conclusion — its quality, its corroboration, and the assumptions the conclusion rests on. In ASOM-Fed a fused assessment without a confidence level is incomplete, because a decision made on a high-confidence assessment and one made on a low-confidence assessment should not be the same decision.

Not to be confused with

Certainty, or emphasis. “High confidence” used as an intensifier destroys the field’s information content. A confidence scale is only working if low confidence is published sometimes.

Where it is used

Course of action

COA
Doctrinal origin

ATP 2-01.3 and ATP 2-33.4. The last of four fixed IPB steps — define the operational environment, describe environmental effects, evaluate the threat, determine threat courses of action — so a COA is built on a terrain that has already been defined, never sketched first.

On a federal network

A specific, terrain-grounded way an adversary could reach an objective — an avenue of approach, the maneuvers that would carry it, and what would have to be true first. ASOM-Fed models the most likely and the most dangerous threat COA against the Federal Reference Agency and scores how much of each the coverage baseline actually answers.

Not to be confused with

The defender’s own plan, or a runbook. A threat COA describes what the adversary might do; nothing in it is an instruction to the defense. A scheme of maneuver is the defender’s answer to it, and the two are authored by different roles for different reasons.

Where it is used

Coverage

Doctrinal origin

Not doctrinal in this sense; the term here comes from the Defense Tower Model’s allocation arithmetic rather than from maneuver doctrine.

On a federal network

The weighted proportion of defensive requirement that is actually met on a given piece of terrain, rolled up from sub-towers to towers to missions. Each sub-tower’s maturity gives it a coverage percentage; those are weighted by defensive weight and aggregated. Coverage is only meaningful with its denominator visible — it rises whenever elements leave the population, which is why terrain currency (TM-6) and layer classification (TM-2) are prerequisites for believing the number.

Not to be confused with

Compliance percentage. Compliance counts controls implemented against a baseline; coverage weights protection against what the estate is worth and how exposed it is. A program can be fully compliant and thinly covered on its main effort.

CPE

Cyber Preparation of the Environment
Doctrinal origin

The cyber analogue of Intelligence Preparation of the Battlefield: define the operational environment, describe its effects, evaluate the threat, determine threat courses of action.

On a federal network

The Map step of the cycle. Refresh the terrain overlay, enumerate avenues of approach, and build most-likely and most-dangerous threat courses of action against the ground as it currently is. CPE is what makes the rest of the cycle intelligence-led rather than alert-led: it produces the map that the scheme of maneuver is drawn on.

Not to be confused with

Asset inventory. Inventory establishes what exists; CPE establishes what that means positionally — what is reachable from where, and what an adversary would do about it.

Culminating point

Doctrinal origin

Operational art. The point at which a force can no longer sustain its operation — where the attacker can no longer press the attack, or the defender can no longer hold.

On a federal network

The defender’s culminating point is analyst saturation: the alert volume, incident concurrency or change rate beyond which the decision loop lengthens and quality falls. It is a real, measurable threshold and it is reached quietly. ASOM-Fed makes it a declared trigger (TA-5) rather than a discovery, so that the program sheds load deliberately instead of degrading invisibly. The adversary has one too, and imposing cost is an attempt to reach it first.

Not to be confused with

Burnout, or a staffing complaint. Culmination is an operational condition with an observable signature in the tempo numbers, not a morale problem — and the response is to change what the force is attempting, not to ask it to try harder.

Where it is used

Cyber terrain overlay

Doctrinal origin

The graphical overlay: a single map on which terrain, obstacles and control measures are drawn, from which everyone works.

On a federal network

The one authoritative positional picture of the estate — every system, data store and external actor as a distinct element, placed inside a trust zone whose boundary is actually enforced, with its connections recorded. It is the input to almost everything else in the framework, which is why a program that skips it starves decisive-point identification, reachability analysis and coverage computation simultaneously. Competing diagrams are retired when it is published; two maps is the same as none.

Not to be confused with

A network diagram. A network diagram shows topology. An overlay adds position relative to trust, weight, ownership and the denied paths that were chosen deliberately.

D

Decisive point

Doctrinal origin

Operational art. A place, key event or system whose seizure gives a marked advantage over the enemy or contributes materially to achieving success.

On a federal network

The small number of elements whose compromise unhinges the wider defense — where control is decided, not merely where value sits. In a federal estate the two usual candidates are the identity policy decision point and the build pipeline: capture either and everything downstream follows without further effort. Designation is a recorded decision with a written justification in terms of what the adversary gains, and it must be discriminating. A designation covering most of the estate has designated nothing.

Not to be confused with

Key terrain, and crown jewels. Key terrain is ground whose control confers advantage; a decisive point is where control of the wider system is decided. The sensitive records store is key terrain and is usually the objective; the identity plane is the decisive point, and it is often not on anyone’s crown-jewel list.

Where it is used

Defensive weight

Doctrinal origin

Not doctrinal; the allocation driver of the Defense Tower Model, analogous to a cost driver in cost-transparency practice.

On a federal network

Criticality × Exposure, each scored 1–5, giving every element a comparable 1–25 measure of how much it matters. Criticality comes from the mission consequence of loss — not from the size or cost of the system. Exposure comes from reachability by untrusted actors, read off the connection register rather than estimated. Weight is what makes prioritization arithmetic instead of argument, and what lets coverage roll up as a weighted average rather than a count.

Not to be confused with

A risk score. A risk score usually multiplies likelihood by impact and answers “how worried should I be”. Defensive weight answers “how much of the defensive effort should this element attract”, and is deliberately independent of any particular threat.

Where it is used

Denied path

Doctrinal origin

Obstacle and control-measure practice: a route deliberately closed, recorded on the overlay as a decision so that it is not reopened by someone who did not know why it was shut.

On a federal network

A connection between two elements that has been deliberately prevented, recorded distinctly from the mere absence of a connection, with the control that enforces it named. The distinction matters because the two look identical in a firewall export and behave completely differently over time: an absence is reopened by the next change request; a denied path has an owner, a rationale, and a monitor.

Not to be confused with

A missing connection. Most pairs of elements have no connection and never needed one. A denied path is the subset where somebody decided, and that decision has to survive the person who made it.

Where it is used

F

Fires

Doctrinal origin

The delivery of effects against a target. In doctrine, fires are planned, authorized, and delivered under engagement rules that say what may be engaged without asking.

On a federal network

Active defensive actions: revoke a session, quarantine a host, block infrastructure, sever a segment, deploy a decoy. The word is used deliberately, because it brings engagement authority with it — every fire is either pre-authorized in the rules of engagement or requires the Authorizing Official, and the proportion that is pre-authorized is one of the framework’s headline measures of performance.

Not to be confused with

Automation. Automation is how a fire is delivered; authorization is whether it may be. A fully automated response outside the rules of engagement is faster and worse.

Where it is used

Form of maneuver

Doctrinal origin

The durable categories a scheme is assembled from — envelopment, penetration, turning movement and the rest — chosen because categories outlive the perishable techniques that implement them.

On a federal network

One of the eleven defensive forms in the ASOM-Fed catalog: screen, defense in depth, envelopment, obstacle emplacement, ambush, delay, counterattack, isolation, spoiling attack, exploitation and pursuit, reconstitution. A form is intent-first — leaders pick the form, engineers pick the technique. That separation is what lets the framework survive tool churn: 154 cataloged techniques will change, the eleven forms will not.

Not to be confused with

A product category, or a control family. A form is what you are trying to do to the adversary. The technique is how, and the control is how an assessor knows you did.

Where it is used

K

Key terrain

Doctrinal origin

Terrain analysis. Any locality or area whose seizure or retention affords a marked advantage to either combatant.

On a federal network

Systems and data whose control confers decisive advantage — the identity plane, the public service portal, sensitive pre-decisional records, mission-staff workflow. Key terrain is where the campaign’s effort is concentrated, and the ASOM-Fed measure of performance “key terrain behind a policy enforcement point” is the crudest useful test of whether that concentration is real.

Not to be confused with

High-value assets, and everything important. Key terrain is defined by advantage to *either* side: ground the adversary would benefit from holding is key terrain even when it holds nothing valuable of yours. A jump host is a good example.

Where it is used

M

Main effort

Doctrinal origin

Mission command. The single activity the commander designates as most important to success, which receives priority of support when resources are contested.

On a federal network

The one place defensive mass and priority are concentrated this cycle — typically the identity plane plus the crown-jewel record set. Designation only means something at the moment of contention: when the backlog, the budget and the on-call attention cannot all go to everything, the main effort wins by prior decision rather than by argument.

Not to be confused with

The top of a priority list. A ranked list of ten priorities has no main effort. If designating it did not cause something else to be visibly deprioritized, it was not designated.

Where it is used

Measure of effectiveness

MOE
Doctrinal origin

Assessment doctrine. A criterion used to assess changes in system behavior, capability or the operational environment — “are we winning?”

On a federal network

A measure of whether executing the maneuvers changed the outcome. In ASOM-Fed: temporal advantage, positional advantage, cost imposition, resilience, and the zero-trust maturity vector. These are the measures capable of reporting that a busy program is losing, which is precisely why they are harder to collect and easier to quietly drop.

Not to be confused with

A measure of performance. See the assessment guide — the distinction is the single most load-bearing idea in the framework’s measurement layer.

Measure of performance

MOP
Doctrinal origin

Assessment doctrine. A criterion used to assess friendly actions tied to task accomplishment — “are we doing the maneuvers right?”

On a federal network

A measure of execution: percentage of key terrain behind a policy enforcement point, deception coverage of the data terrain, percentage of fires pre-authorized, overlay freshness, intelligence requirements answered per cycle. Every one of these can be excellent while the defense is losing. They are necessary, cheap to collect, and dangerous alone.

Not to be confused with

Effectiveness. A dashboard composed entirely of measures of performance is the normal condition of a security program, and it is the condition this framework exists to interrupt.

Mobility corridor

Doctrinal origin

Terrain analysis. Ground within an avenue of approach that permits movement and maneuver — the part of the route a force can actually move along, as opposed to the route in the abstract.

On a federal network

The lateral-movement paths inside the estate: flat network segments, over-permissioned service accounts, shared cloud roles, trust relationships between tenancies. An avenue of approach describes how an adversary gets toward an objective; the mobility corridor is the ground they move along once inside, and it is the natural target for canalization — you cannot close every corridor, so you narrow them until movement happens where you are watching.

Not to be confused with

An avenue of approach. The avenue is the route to the objective; the corridor is the movable ground within it. A service account with rights across four systems is a corridor, not an avenue.

Where it is used

O

Obstacle

Doctrinal origin

Obstacle doctrine. Anything that stops, impedes or diverts movement. Obstacles are emplaced to a purpose — to turn, block, fix or disrupt — and are covered by observation and fire, or they are merely inconvenient.

On a federal network

A control that shapes adversary movement rather than merely existing: segmentation, phishing-resistant multi-factor authentication, conditional access, egress control. The doctrinal condition carries over exactly — an obstacle that is not observed does not impede for long, which is why maneuver assignment (SM-2) and barrier sufficiency (KT-5) both ask what watches the obstacle, not only whether it is in place.

Not to be confused with

A security control in general. Most controls are protective rather than shaping. An obstacle is one placed on a specific route, with a specific effect intended on a specific movement.

Where it is used

P

PCIR

Priority Cyber Intelligence Requirement
Doctrinal origin

Priority intelligence requirements: the small set of questions the commander needs answered to make a decision, stated in advance, driving collection rather than describing it afterwards.

On a federal network

The two to five questions the defense needs answered this cycle, each tied to a decision somebody will make — “are external-user accounts being taken over at a rate above baseline?”, “has our build pipeline been touched by the tradecraft in the current advisory?”. Requirements are set at Frame and closed at Assess; the count answered per cycle against the count set is a headline measure of performance.

Not to be confused with

A collection wish list, or a threat-intel subscription. A requirement that no decision depends on will not be answered under pressure, and should not have been set.

Where it is used

Phase

Doctrinal origin

Joint campaign phasing: shape, deter, seize initiative, dominate, stabilise, enable civil authority. Phasing exists so that effort has a shape over time and a main effort per period.

On a federal network

A declared statement of what the defense is currently trying to do — shaping conditions, deterring, contesting first contact, defeating an attempt, restoring secure operations, or handing back to steady state. Declaring the phase changes what “good” looks like: the maneuvers that dominate, the resourcing, and the tolerance for disruption all differ between shape and dominate. An undeclared phase means the program is permanently in an undifferentiated grind.

Not to be confused with

An incident severity level. Severity describes one event; a phase describes the posture of the whole campaign, and can be declared with no incident in progress at all.

Where it is used

Positional advantage

Doctrinal origin

Maneuver. Advantage derived from where you are relative to the adversary and the ground, as distinct from advantage derived from mass or firepower.

On a federal network

The share of adversary attempts canalized into instrumented terrain, and the share stopped before reaching data terrain. Positional advantage is what obstacles, canalization and deception buy: not fewer attempts, but attempts happening on ground you own and observe. It is a measure of effectiveness, and it moves slowly.

Not to be confused with

Coverage. Coverage says how much protection is in place; positional advantage says whether the adversary is being forced onto your ground. High coverage evenly spread can produce very little positional advantage.

Pre-authorized fires

Doctrinal origin

Engagement authority. The set of engagements a subordinate may prosecute without referring back — the mechanism by which a force acts at the speed of the situation rather than the speed of its command chain.

On a federal network

The defensive actions the SOC may execute without escalation: revoke a session on confirmed account takeover, quarantine an endpoint, block named infrastructure. Everything else needs the Authorizing Official — degrading a public service, for instance. This list is the single largest lever on defensive tempo that leadership controls, and its width should be a deliberate decision reviewed each cycle rather than an artifact of whoever was nervous when it was written.

Not to be confused with

Automation, and blanket delegation. A pre-authorized fire is bounded and reversible by design, and it is recorded when it executes; delegation without those properties is not engagement authority, it is an absence of it.

Where it is used

R

Reachability

Doctrinal origin

Not doctrinal; the graph-theoretic core of the avenue-of-approach question, made binary on purpose.

On a federal network

Whether an adversary starting from a declared position can arrive at a decisive point across permitted paths. The assessment runs on permitted paths only — a denied path is not a route unless it fails — and starts from every declared threat-actor position, not only the internet. The answer is recorded every cycle whichever way it comes out; where a point is reachable, the shortest path becomes the remediation target, and where it is not, the specific denied paths preventing it become the barrier set.

Not to be confused with

Exploitability. Reachability says a path exists; it says nothing about whether the adversary can defeat the controls along it. Treating reachable as compromised overstates; treating unreachable as safe forgets that the answer changes the moment a barrier is removed.

Where it is used

Reconstitution

Doctrinal origin

The deliberate restoration of a degraded force to a required level of capability — a planned operation with its own resourcing, not the residue of a failed one.

On a federal network

Restoring the mission on evidence rather than on hope. Declared recovery time and recovery point objectives per mission service, means of recovery held outside the production identity plane, a trusted rebuild path that covers the identity plane itself, restored data verified against an independent integrity record, and the whole thing exercised on a stated cadence. The indicator is not that a plan exists but that every recovery objective has been demonstrated inside its stated period.

Not to be confused with

Backup, and disaster recovery. Backups are a component. Reconstitution assumes the adversary had access to the production environment — including its identity plane and possibly its backups — and asks what is left that can be trusted.

Residual risk

Doctrinal origin

Risk management. What remains after controls are applied — the part that is carried rather than treated.

On a federal network

The inverse of coverage, weighted and rolled up the same way, so that it lands on a named mission rather than on the estate in aggregate. Its value is that it is stated as a number attached to a consumer, which makes it something an Authorizing Official can accept in writing (CG-4) instead of something that accumulates unremarked in a register.

Not to be confused with

Accepted risk. Residual risk is computed; accepted risk is decided. Risk that is residual and unaccepted is the normal state of every program, and it is exactly the population findings disposition is meant to keep shrinking.

Rules of engagement

ROE
Doctrinal origin

Directives that define the circumstances and limitations under which force may be applied. They exist to make delegated action lawful and fast at once.

On a federal network

The standing statement of which defensive actions may be executed without escalation, by whom, against what, and with what recording obligation — plus what requires the Authorizing Official. Governance owns the document, the SOC drafts what it needs to operate, the Authorizing Official approves it. Without it, every containment decision is an escalation, and tempo is capped by the availability of an executive.

Not to be confused with

An incident response plan. A response plan describes a process; the rules of engagement describe authority. A program can have an excellent plan and no authority to execute it at 03:00.

Where it is used

Running estimate

Cyber Running Estimate
Doctrinal origin

Staff practice. A continuously updated assessment maintained by each staff section — current situation, projected situation, and the recommendation that follows — kept live rather than produced on request.

On a federal network

The living situational picture the SOC and hunt work from and the intelligence cell fuses into: what is currently believed about the ground, the adversary and the defense, with confidence attached, updated continuously rather than assembled for a meeting. It is also the artifact that turns out to be audit evidence of a functioning, continuously-monitored program — which is a by-product, not the purpose.

Not to be confused with

A dashboard, or the cycle brief. A dashboard shows current values; a running estimate carries judgment and projection. The brief (CE-7) is a periodic extract from the estimate, not the estimate itself.

Where it is used

S

Scheme of maneuver

Doctrinal origin

The central narrative of an operation order: how the force will array and move, in what sequence, to gain positional advantage — with one designated main effort.

On a federal network

The defensive campaign plan: which forms of maneuver apply, on which terrain, in what sequence, with which main and supporting efforts, and with branches and sequels attached. Screen → Ambush → Delay → Counterattack → Exploitation is a scheme; a list of purchased products is not. The scheme is a deliverable — one graphic and a narrative — and it is what the Authorizing Official actually approves.

Not to be confused with

A security architecture, or a roadmap. Architecture describes what is built; a roadmap describes what will be bought and when. A scheme of maneuver describes what you intend to do to an adversary on ground you have mapped.

Sequel

Doctrinal origin

Operational planning. A subsequent operation based on the possible outcomes of the current one — win, lose, or stalemate — planned before the current one concludes.

On a federal network

What the defense does after this engagement ends, planned in advance for each plausible outcome. After a repelled intrusion: harvest indicators into detections, close the exploited avenue, update the overlay and the intelligence requirements, and share to the community. After a successful intrusion: reconstitution, and a terrain picture that has changed. The point of pre-planning is that the hours after an incident are the hours when nobody has the attention to plan.

Not to be confused with

A branch, and a lessons-learned process. A sequel is a planned next operation with its own resourcing, decided before the outcome is known — not a retrospective held afterwards.

Where it is used

Supporting effort

Doctrinal origin

Mission command. An effort that enables the main effort, and which is resourced after it — the ordering is the whole point.

On a federal network

Defensive work whose purpose is to make the main effort succeed: endpoint detection on mission-staff workstations and the log pipeline, when the main effort is the identity plane and the crown-jewel records. Supporting efforts are legitimate, funded and necessary. They lose the argument when resources are contested, and knowing that in advance is what makes the designation useful.

Not to be confused with

Lower priority work in general. A supporting effort is defined by its relationship to the main effort, not by its rank on a list. Work that supports nothing is not a supporting effort; it is unassigned.

Where it is used

T

Tempo

Doctrinal origin

The relative rate of military action. Tempo is comparative by definition — it has no meaning except against an adversary’s rate.

On a federal network

The rate at which the defense detects, decides and acts, measured against the rate at which the adversary advances and adapts. ASOM-Fed measures the defender side directly (TA-1) and estimates the adversary side (TA-2), and declares a threshold below which the deficit escalates (TA-3). Tempo is also degradable: TA-5 requires a declared trigger for the conditions under which the defense is no longer keeping up, so that load is shed deliberately.

Not to be confused with

Speed, or mean time to respond in isolation. A four-hour containment time is excellent against a three-day intrusion and irrelevant against a twenty-minute one. Reporting the defender’s number alone is the most common way tempo is claimed without being measured.

Temporal advantage

Doctrinal origin

From the cyber-maneuver literature: cyber maneuver seeks physical, technical, and cognitive positional *and temporal* advantage over an adversary.

On a federal network

The defender’s decision tempo — detect to decide to contain — set against adversary dwell time. It is the signature ASOM-Fed metric and the one that can be honestly lost: a cycle is won when temporal advantage is positive at a stated confidence level. Positive means the defender’s loop closes faster than the adversary can adapt, not merely that a service was restored.

Not to be confused with

Mean time to detect. Detection is one of three timestamps, and it is the one most easily improved without changing the outcome. An advantage computed from detection alone omits the decision, which is where most of the delay actually lives.

Trust zone

Doctrinal origin

Control measures: boundaries drawn on the overlay that define where a unit may operate and who is responsible inside them.

On a federal network

A grouping of elements sharing a boundary that is actually enforced by a named technical control. The definition is deliberately strict — zones that exist on paper but are not technically enforced are recorded as findings, not as zones — because “inside” and “outside” have to be properties of the model rather than assumptions in somebody’s head. Every element sits in exactly one zone, and a new element defaults to none until placed.

Not to be confused with

A network segment, or a security domain. A segment is one possible enforcement mechanism. A zone is defined by the enforcement, whatever it is — a policy enforcement point in front of an application is a zone boundary without a VLAN anywhere in sight.

Where it is used
Elsewhere in the Apparatus

The Rest of the Reference Layer.