1200kmSECURITY RESEARCH
Loading interactive filters…

1200KM / simulation

T0828 Loss of Productivity and Revenue — Attack Simulation

Adversaries may cause loss of productivity and revenue through disruption and even damage to the availability and integrity of control system operations, devices, and related processes. This technique may manifest as a direct effect of an ICS-targeting attack or tangentially, due to an IT-targeting attack against non-segregated environments. In cases where these operations or services are brought to a halt, the loss of productivity may…

Complete technique description

Adversaries may cause loss of productivity and revenue through disruption and even damage to the availability and integrity of control system operations, devices, and related processes. This technique may manifest as a direct effect of an ICS-targeting attack or tangentially, due to an IT-targeting attack against non-segregated environments.

In cases where these operations or services are brought to a halt, the loss of productivity may eventually present an impact for the end-users or consumers of products and services. The disrupted supply-chain may result in supply shortages and increased prices, among other consequences.

A ransomware attack on an Australian beverage company resulted in the shutdown of some manufacturing sites, including precautionary halts to protect key systems. [Paganini, Pierluigi June 2020] The company announced the potential for temporary shortages of their products following the attack. [Paganini, Pierluigi June 2020] [Lion Corporation June 2020]

In the 2021 Colonial Pipeline ransomware incident, the pipeline was unable to transport approximately 2.5 million barrels of fuel per day to the East Coast. [Colonial Pipeline Company May 2021]

Official technique definition · Open in the interactive matrix

Detection telemetry and configuration

These contracts are selected through exact technique-to-data-component relationships or explicitly labelled planning overrides. Configure a collector at the relevant observation point; a telemetry name alone is not coverage.

Analyst-proposed lab instrumentation, not an official ATT&CK component mapping or a validated detection. It may observe effects without establishing malicious intent.

Production throughput and downtime · planning input

proposed-production-throughput-and-downtime collection page — Export approved production counters and downtime intervals with baseline, units and change-ticket context.

Providers and collection configuration

  • Agree the measurement points, read-only interfaces, sampling intervals and safety boundary with the process owner. Use a simulator or non-production fixture.
  • Subscribe to supported audit/alarm events or approved historian exports. Preserve source timestamp, quality, engineering units, asset/tag identity and clock offset.
  • Compare independent measurements and record gaps/latency. Do not enable intrusive polling, change controller logic or alter safety setpoints merely to generate logs.

Required normalized fields: line, units_per_minute, baseline_units_per_minute, downtime_seconds.

Illustrative collection event

Project-normalized synthetic JSON, not a native provider log, captured event, attack verdict or validated detection. A parser/adapter is required for a real SIEM. Example names, IPs and values are fictional.

{
  "schema": "1200km.telemetry.example.v1",
  "synthetic": true,
  "timestamp": "2026-09-27T12:00:00Z",
  "telemetry_id": "proposed-production-throughput-and-downtime",
  "collector": "illustrative-lab-collector",
  "observation": {
    "line": "lab-fixture",
    "units_per_minute": 8,
    "baseline_units_per_minute": 10,
    "downtime_seconds": 0
  }
}

Visibility limits: There is no universal PLC event ID or configuration command. Visibility depends on vendor, protocol and process. An alarm or process deviation demonstrates an effect, not necessarily a cyberattack.

Business impact records · planning input

proposed-business-impact-records collection page — Use approved downtime/incident exports with timestamps, attribution confidence and process-owner review.

Providers and collection configuration

  • Agree the measurement points, read-only interfaces, sampling intervals and safety boundary with the process owner. Use a simulator or non-production fixture.
  • Subscribe to supported audit/alarm events or approved historian exports. Preserve source timestamp, quality, engineering units, asset/tag identity and clock offset.
  • Compare independent measurements and record gaps/latency. Do not enable intrusive polling, change controller logic or alter safety setpoints merely to generate logs.

Required normalized fields: incident_id, service, downtime_minutes, cause.

Illustrative collection event

Project-normalized synthetic JSON, not a native provider log, captured event, attack verdict or validated detection. A parser/adapter is required for a real SIEM. Example names, IPs and values are fictional.

{
  "schema": "1200km.telemetry.example.v1",
  "synthetic": true,
  "timestamp": "2026-09-27T12:00:00Z",
  "telemetry_id": "proposed-business-impact-records",
  "collector": "illustrative-lab-collector",
  "observation": {
    "incident_id": "LAB-42",
    "service": "fixture-line",
    "downtime_minutes": 5,
    "cause": "undetermined"
  }
}

Visibility limits: There is no universal PLC event ID or configuration command. Visibility depends on vendor, protocol and process. An alarm or process deviation demonstrates an effect, not necessarily a cyberattack.

Detection rules and analytic guidance

Open the dedicated detection workspace · Existing query engineering

DET0757 Detection of Loss of Productivity and Revenue

MITRE detection strategy

AN1889 Analytic 1889

No standard detection method currently exists for this technique.

Platforms: None.

No structured log-source mapping supplied by this analytic.

Source rule directory and observation requirements

No exact-tagged Sigma source rule was imported. This does not establish that the technique is undetectable; the MITRE guidance and collection requirements remain relevant.

Before treating a rule as coverage

  1. Read the actual condition and logsource; identify attacker-side, victim-side or third-party visibility.
  2. Map native sensor fields, parse times and identities, then compile for the selected backend.
  3. Replay a behavior-positive case, a normal control, an authorized look-alike and a missing-telemetry case.
  4. Record matches and misses with rule version and source events. No match is inconclusive when required telemetry is absent.

Anomaly-based detection

No exact technique-specific Atlas model is present for T0828 in the selected source snapshot. The following is a design worksheet, not a newly validated model.

Anomaly engineering worksheet

Start from the exact analytic above. The collection-specific lenses below are analyst recommendations; they do not assert that an arbitrary statistical deviation detects this technique.

  • Industrial operations and physical process: Per asset, operating mode and engineering change window: deviations in command/state sequences, measurement residuals and communication freshness. Use a simulator or approved test rig; never generate hazardous physical effects.
  1. Define an entity/peer group and feature; exclude the evaluation period from baseline training.
  2. Use representative normal and maintenance activity. Do not invent a production threshold from a synthetic example.
  3. Evaluate held-out behavior-positive and benign cases; measure false positives, misses and telemetry loss separately.
  4. Keep abnormality separate from maliciousness. Correlate with the behavior-specific source evidence.

Anomaly Detection Atlas · Baseline, validation and blind spots

Attack tools and documented software

No reviewed lab-tool association is selected for this exact technique. This is a curation gap, not a statement that no tool can implement the behavior.

Software observed in source procedures

These are exact ATT&CK software-use relationships, including malware. They provide behavior context, not recommendations to download or execute malware. No safety or detector claim is inherited.

7 source-documented software associations
  • S0368 NotPetya — malware.

    NotPetya disrupted manufacturing facilities supplying vaccines, resulting in a halt of production and the inability to meet demand for specific vaccines. [David Voreacos, Katherine Chinglinsky, Riley Griffin December 2019]

    Exact relationship: relationship--7258c355-677c-452d-b1fc-27767232437b
  • S0372 LockerGoga — malware.

    While Norsk Hydro attempted to recover from a LockerGoga infection, most of its 160 manufacturing locations switched to manual (non-IT driven) operations. Manual operations can result in a loss of productivity. [Kevin Beaumont][Hydro]

    Exact relationship: relationship--46bc86e4-e20b-4778-80d2-8891039e6fb4
  • S0446 Ryuk — malware.

    An enterprise resource planning (ERP) manufacturing server was lost to the Ryuk attack. The manufacturing process had to rely on paper and existing orders to keep the shop floor open. [Kelly Jackson Higgins]

    Exact relationship: relationship--383e242a-72d4-4b40-8905-888595c34919
  • S0496 REvil — malware.

    The REvil malware gained access to an organizations network and encrypted sensitive files used by OT equipment. [Selena Larson, Camille Singleton December 2020]

    Exact relationship: relationship--ab306654-2abb-4983-8d30-df4058adb06c
  • S0605 EKANS — malware.

    EKANS infection resulted in a temporary production loss within a Honda manufacturing plant. [Davey Winder June 2020]

    Exact relationship: relationship--a6519c11-e9d4-4b6f-8d92-8efaa2144c28
  • S0606 Bad Rabbit — malware.

    Several transportation organizations in Ukraine have suffered from being infected by Bad Rabbit, resulting in some computers becoming encrypted, according to media reports. [ESET Bad Rabbit]

    Exact relationship: relationship--d7ea83fa-87c7-4d36-96d5-aee554504040
  • S0608 Conficker — malware.

    A Conficker infection at a nuclear power plant forced the facility to shutdown and go through security procedures involved with such events, with its staff scanning computer systems and going through all the regular checks and motions before putting the plant back into production. [Catalin Cimpanu April 2016]

    Exact relationship: relationship--51f9963c-c041-4bec-b482-5fda2fb5bca4

Simulation design and documented procedures

Atomic evidence: no compatible candidate in this snapshot. Live lab status: not run for these imported procedures.

Use a process simulator or isolated test rig with no connection to production controllers or physical actuators. Preserve safety interlocks; destructive effects require synthetic evidence, not real equipment damage.

No compatible Atomic procedure is present in this pinned evidence set. Technical feasibility has not been ruled out. A custom procedure must define the behavior, target, collection point, success observable and rollback before execution.

Technique-specific experiment contract

  1. Choose one procedure implementing T0828 Loss of Productivity and Revenue; identify the observable behavior in the source definition, not just its tactic.
  2. Record exact target, tool/version, inputs, privileges, network limits and approval. Never run an imported default target automatically.
  3. Enable the collection sources above and verify a benign baseline reaches the detector.
  4. Run only the approved isolated scenario; capture native events and an independent behavior observable.
  5. Evaluate the exact rule/model, restore the lab, and preserve configuration, event hashes, alerts, controls and misses.

Synthetic logs and offline contract check

Download synthetic collection fixture (JSON) · Download the complete engineering workbook

This fixture exercises the listed collection fields. It does not reproduce Loss of Productivity and Revenue, label its example events as malicious, or measure detection effectiveness. Use the exact analytic and selected procedure to build an independently labelled behavior-positive dataset.

Not run in this browser. No network scan or attack command is executed by this control.

Validation status and remaining work

Source identity
Joined by exact technique/object IDs against hash-pinned sources.
Collection fixture
Available for offline schema exercises; not attack emulation.
Native telemetry / backend / real attack
Not validated for these imported procedures. Source fidelity and page tests cannot establish sensor or detector effectiveness.

All-page audit and evidence inventory · This page’s machine-readable workbook

Sources and evidence boundaries

Pinned MITRE STIX source · SHA-256 c9ca0ce523a1b5e512060a390415e8aefe8f6d32c5f82d7de81264960c1e1183. Definition and procedure context are reproduced from this snapshot, not independently re-investigated incidents.

Source-linked mitigations
  • M0953 Data Backup

    Take and store data backups from end user systems and critical servers. Ensure backup and storage systems are hardened and kept separate from the corporate network to prevent compromise. Maintain and exercise incident response plans [Department of Homeland Security October 2009], including the management of gold-copy back-up images and configurations for key systems to enable quick recovery and response from adversarial activities that impact control, view, or availability.

Connected ecosystem references

Linked tags

icsics-otimpactisolated_authorized_labprocedure_review_requiredtelemetry_configuration_requiredot_fixture_and_process_safety_reviewpotential_disruption_requires_individual_review
No Atomic candidate in snapshottechniqueno_standard_source_mapping

Detection and collection

T0828 detection workspace

No reviewed association in this snapshot.

Pinned research references. No browser attack runner or production-validated detector is asserted. Imported procedures remain unvalidated; any bounded lab evidence has its own scope. ATT&CK / Atomic provenance · Detection provenance.