# Engineering stations and project integrity

Manage project files, revisions, removable media and legacy-system risks with process context; a running workstation is not a validated system.

Original AI-assisted SecNet educational content. Fictional local examples; not a standards provider publication, endorsement or compliance evidence. Page exercises do not create account progress.

Sources checked: 2026-10-21

## The engineering-station role

Engineering stations can mediate privileged operations involving projects and control logic. Treating them like routine office computers can merge distinct trust areas. Harbor records who can access each project revision, maintenance privileges and separation from normal-use identities. Unsupported agents or protection software are not installed on assumption; assess compatibility and operating effects. This lesson provides no installation or control-logic modification procedure. Learners justify the minimum access needed for a task and a supported control approach, including how exceptions will be owned and revisited.

## Approved revision and integrity

A matching hash is narrow evidence that bytes match; it does not alone establish the correct revision, legitimate origin or safe logic. Keep the approved project ID, vendor-tool revision, change reference and review record together. Harbor asks whether the backed-up project contains the last accepted change. A difference prompts reconciliation by the revision owner rather than automatic loading to the plant. Real logic comparison and field validation belong to authorized engineering. The exercise uses only synthetic textual evidence fields and performs no controller upload, download or process operation.

## Removable media and transfer

A USB scan reports results of particular checks on content; it does not validate authorization, business need or target compatibility. Review authorized media, an appropriate transfer point, file origin and target-process approval separately. Harbor asks who supplied it, for which project, under what review and when use ended. A direct transfer from an internet-connected computer to a control network requires an explicitly designed process rather than assumed acceptance. Learners connect no media; they evaluate missing fields in synthetic records and explain why a clean scan alone is insufficient.

## Legacy platform and lifecycle

A legacy system that still runs is not necessarily supported or adequately protected. Record vendor support, spare parts, tool licensing, installation media and specialist dependencies. When replacement is not immediately possible, define compensating-control scope, ownership, measurable evidence and review dates. Compensation is not indefinite risk acceptance. Harbor marks restricted privileged access as an assumption whose real effectiveness would need validation. Link project-integrity and lifecycle risks to procurement and maintenance planning, so an exception has an owner and a practical replacement path rather than a permanent label.

## Working sequence

1. Record engineering roles and privileges.
2. Match project revisions to change records.
3. Review media origin and transfer evidence.
4. Identify support and rebuild dependencies.
5. Record integrity gaps and replacement plans.

## 1. Is the backup the correct revision?

Backup-file existence is insufficient. Without approved revision, change linkage and integrity review, the process state represented by the restored content remains uncertain.

This code is a local policy model; it does not replace actual equipment, process or safety assessment.

### Weak implementation
```js
s => s.backupExists === true
```

### Corrected implementation
```js
s => s.backupExists === true &&
  s.approvedVersion === true &&
  s.changeReference === true &&
  s.integrityReviewed === true
```

### Synthetic input and actual model output
```json
{
  "before": [
    {
      "name": "documented-case",
      "input": {
        "backupExists": true,
        "approvedVersion": true,
        "changeReference": true,
        "integrityReviewed": true
      },
      "expected": true,
      "observed": true,
      "matched": true
    },
    {
      "name": "missing-approvedVersion",
      "input": {
        "backupExists": true,
        "approvedVersion": false,
        "changeReference": true,
        "integrityReviewed": true
      },
      "expected": false,
      "observed": true,
      "matched": false
    },
    {
      "name": "missing-changeReference",
      "input": {
        "backupExists": true,
        "approvedVersion": true,
        "changeReference": false,
        "integrityReviewed": true
      },
      "expected": false,
      "observed": true,
      "matched": false
    }
  ],
  "after": [
    {
      "name": "documented-case",
      "input": {
        "backupExists": true,
        "approvedVersion": true,
        "changeReference": true,
        "integrityReviewed": true
      },
      "expected": true,
      "observed": true,
      "matched": true
    },
    {
      "name": "missing-approvedVersion",
      "input": {
        "backupExists": true,
        "approvedVersion": false,
        "changeReference": true,
        "integrityReviewed": true
      },
      "expected": false,
      "observed": false,
      "matched": true
    },
    {
      "name": "missing-changeReference",
      "input": {
        "backupExists": true,
        "approvedVersion": true,
        "changeReference": false,
        "integrityReviewed": true
      },
      "expected": false,
      "observed": false,
      "matched": true
    }
  ]
}
```

## 2. A clean USB scan

A clean scan supplies neither authorization nor process approval. Review authorized media, transfer point and target suitability; this scenario uses no media on a real device.

This code is a local policy model; it does not replace actual equipment, process or safety assessment.

### Weak implementation
```js
s => s.mediaScanned === true
```

### Corrected implementation
```js
s => s.mediaScanned === true &&
  s.mediaAuthorized === true &&
  s.transferStation === true &&
  s.processApproval === true
```

### Synthetic input and actual model output
```json
{
  "before": [
    {
      "name": "documented-case",
      "input": {
        "mediaScanned": true,
        "mediaAuthorized": true,
        "transferStation": true,
        "processApproval": true
      },
      "expected": true,
      "observed": true,
      "matched": true
    },
    {
      "name": "missing-mediaAuthorized",
      "input": {
        "mediaScanned": true,
        "mediaAuthorized": false,
        "transferStation": true,
        "processApproval": true
      },
      "expected": false,
      "observed": true,
      "matched": false
    },
    {
      "name": "missing-processApproval",
      "input": {
        "mediaScanned": true,
        "mediaAuthorized": true,
        "transferStation": true,
        "processApproval": false
      },
      "expected": false,
      "observed": true,
      "matched": false
    }
  ],
  "after": [
    {
      "name": "documented-case",
      "input": {
        "mediaScanned": true,
        "mediaAuthorized": true,
        "transferStation": true,
        "processApproval": true
      },
      "expected": true,
      "observed": true,
      "matched": true
    },
    {
      "name": "missing-mediaAuthorized",
      "input": {
        "mediaScanned": true,
        "mediaAuthorized": false,
        "transferStation": true,
        "processApproval": true
      },
      "expected": false,
      "observed": false,
      "matched": true
    },
    {
      "name": "missing-processApproval",
      "input": {
        "mediaScanned": true,
        "mediaAuthorized": true,
        "transferStation": true,
        "processApproval": false
      },
      "expected": false,
      "observed": false,
      "matched": true
    }
  ]
}
```

## 3. A running legacy system

Running successfully does not establish support or recoverability. Legacy-system risk remains obscured without support status, separated access and a replacement owner.

This code is a local policy model; it does not replace actual equipment, process or safety assessment.

### Weak implementation
```js
s => s.workstationWorks === true
```

### Corrected implementation
```js
s => s.workstationWorks === true &&
  s.supportKnown === true &&
  s.accessSeparated === true &&
  s.replacementOwned === true
```

### Synthetic input and actual model output
```json
{
  "before": [
    {
      "name": "documented-case",
      "input": {
        "workstationWorks": true,
        "supportKnown": true,
        "accessSeparated": true,
        "replacementOwned": true
      },
      "expected": true,
      "observed": true,
      "matched": true
    },
    {
      "name": "missing-supportKnown",
      "input": {
        "workstationWorks": true,
        "supportKnown": false,
        "accessSeparated": true,
        "replacementOwned": true
      },
      "expected": false,
      "observed": true,
      "matched": false
    },
    {
      "name": "missing-replacementOwned",
      "input": {
        "workstationWorks": true,
        "supportKnown": true,
        "accessSeparated": true,
        "replacementOwned": false
      },
      "expected": false,
      "observed": true,
      "matched": false
    }
  ],
  "after": [
    {
      "name": "documented-case",
      "input": {
        "workstationWorks": true,
        "supportKnown": true,
        "accessSeparated": true,
        "replacementOwned": true
      },
      "expected": true,
      "observed": true,
      "matched": true
    },
    {
      "name": "missing-supportKnown",
      "input": {
        "workstationWorks": true,
        "supportKnown": false,
        "accessSeparated": true,
        "replacementOwned": true
      },
      "expected": false,
      "observed": false,
      "matched": true
    },
    {
      "name": "missing-replacementOwned",
      "input": {
        "workstationWorks": true,
        "supportKnown": true,
        "accessSeparated": true,
        "replacementOwned": false
      },
      "expected": false,
      "observed": false,
      "matched": true
    }
  ]
}
```

## Exit evidence

- Approved project/revision/change mapping.
- Media and lifecycle exception record.

## References

- [NIST SP 800-82 Rev.3 · Final September 2023](https://csrc.nist.gov/pubs/sp/800/82/r3/final)
- [NIST SP 1800-10 · Manufacturing system integrity · Final March 2022](https://csrc.nist.gov/pubs/sp/1800/10/final)