Skip to content

Draft — not approved. A working draft by UASK. It may change without notice.

System Construction Framework glossary

Status
Draft
Version
0.1.0
Authority
UASK standard
Applies to
operating-system
Markdown source

Version: 0.1

Each term has one meaning in the whole corpus. A definition here is the meaning; the Home line names the document that states the obligations or the method behind the term, and that statement is not repeated anywhere else. Where a document needs the term it links here.

Two terms were used in two senses in earlier drafts and are now fixed: channel and conformance statement (the per-release record formerly called a “product profile”). The word “profile” now means only the class of system. The words build and withdrawal have one sense each in their entries below.

The glossary defines terms and introduces no obligations. A term used in a rule that is not listed here is a defect of the corpus and is recorded in the corpus backlog.

The standard and its documents

System Construction Framework (SCF)

The brand-independent normative framework for constructing, releasing, maintaining and retiring operating systems. The abbreviation is used after the full name has been given in a document’s title or first mention. Home: index.

Human Interface Framework (HIF)

The companion standard for every human-facing surface of a system. Home: overview, section “Normative hierarchy”.

Corpus

The documents of SCF taken together. Home: overview.

Rule

An identified statement of one obligation, written with a normative word. A rule has an identifier of the form SCF-<GROUP>-<NNN>. The Constitution and the profiles also call a rule a requirement. Home: Construction Constitution.

Rule identifier

The stable, language-independent identifier of a rule. Home: Change policy.

Normative

Creating an obligation for conformance. A statement is normative when it is a rule or when a rule applies it. Home: overview.

Informative

Explaining, illustrating or reporting a fact, and creating no obligation. Examples, guidance, the knowledge base and the platform dossiers are informative. Home: Change policy.

Normative keyword

One of the words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY, read as the overview states. Home: overview, section “Normative words”.

Public interface

The part of SCF that a consumer may rely on across versions; everything else is informative. Home: Change policy.

Consumer

A project that applies SCF and receives it by pinning a Hub release that carries an SCF version. Home: Change policy.

Hub release

A tagged release of the UASK Engineering Hub, the bundle in which SCF is delivered. It is identified by the Hub tag; the version of SCF inside it is a separate number. Home: Change policy.

SCF version

The version of the standard itself: the version of its index document, which a conformance statement names. It is a different number from the Hub tag and from the version of any release of a product. Home: Change policy, SCF-CHG-018.

SCF release

A published state of the corpus of SCF, carrying an SCF version. It is not a release of a product, which is a Release in the sense of the entry below. The words “release” and “MAJOR release” in the Change policy mean an SCF release. Home: Change policy.

Change record

The table at the end of a document of SCF that lists, version by version, the changes made to that document, each with its class. Home: Change policy, SCF-CHG-021.

Parties

Producer

The person or organisation that constructs a system, releases it and answers for it. The Constitution addresses the producer. Home: Construction Constitution.

Recipient

The person or organisation that obtains a release, whether to install it, to run it or to build on it. Home: Construction Constitution.

Operator

The party that runs a system in service and is responsible for administering it, and who may not be the party that built it. Home: Construction Constitution, SCF-HUM-008.

Customer

The party for which a white-label derivative is produced and under whose brand it is delivered to its own users. Home: Profiles, SCF-WLB-005.

Tenant

A party, other than the one that runs a construction service, that submits specifications to it and whose specifications, locks, artefacts and evidence the service keeps apart from those of every other such party. Home: Profiles, SCF-CSV-002, and Construction Constitution, SCF-BLD-012.

Upstream

A project or distribution whose work a system includes or builds on. Home: Construction Constitution, group SCF-SRC.

Derivative

A system built from the artefacts or sources of an upstream distribution. Home: Construction Constitution, SCF-LGL-005, which states what a derivative says about its upstream.

Signing authority

A party outside the producer’s control whose signature a platform requires before it will boot or accept a component. Home: Construction Constitution, SCF-BOOT-005.

The system and its construction

System

The complete operating system product, including its defaults, policy and lifecycle. An image alone is a build artefact, not a system. Home: Construction Constitution, SCF-GOV-001.

Product record

The record in which a product is defined, holding the six elements of SCF-GOV-001: a purpose, an intended deployment context, a threat model, a support period, a data policy and an accountable owner. Home: Construction Constitution, SCF-GOV-001.

Data policy

The product’s statement of what data the system collects or generates, where that data goes and how long it is kept. It is one of the six elements of the product record. Home: Construction Constitution, SCF-GOV-001, with SCF-GOV-008 for residency and group SCF-PRV for collection and retention.

Specification

The declarative description of a system, authored by a human or generated from one. Its identity, spec_id, is a digest of its canonical form. Home: Construction Constitution, group SCF-SPC.

Third-party specification

A specification written by a party other than the one that runs the construction service that builds it. Home: Construction Constitution, SCF-BLD-012.

Lock

The specification with every input resolved to an exact, addressable version. Its identity is lock_id, a content address: the hexadecimal digest of the lock, carried as the text sha256:<digest>. Home: Platform families, section 2, where stages S1 to S3 produce it, and Update and lifecycle, SCF-ULC-002, for its identity.

Closure

The resolved set of the inputs of a selection, including their dependencies, each with its version and digest. Home: Platform families, SCF-PLT-007.

Build

One execution of a lock inside an isolation boundary: stages S4 to S9 of the construction pipeline. The stages before it, which produce the lock, and the stage after it, which attests and signs outside the boundary, are not part of a build; a rule that covers all ten stages speaks of the construction pipeline. Home: Construction Constitution, group SCF-BLD, and Platform families, SCF-PLT-005.

Build record

The record of one pass through the construction pipeline: which stages ran, where and with what result, and where the verification gates fall. The control plane generates the provenance attestation from it. Home: Construction Constitution, SCF-ART-009, and Platform families, SCF-PLT-006.

Isolation boundary

The boundary within which a build executes and which holds under arbitrary code execution inside it. Home: Construction Constitution, SCF-BLD-002.

Construction platform

The build engines, adapters, worker base images, container images and other tooling used to construct a system. It is an input to every build. Home: Construction Constitution, SCF-BLD-009.

Build plane

Not a term of SCF. The one check that uses it, SCF-CHK-062, means the construction platform.

Construction service

The platform that builds systems for others: the builder, its portal, its registry and its workers. It is also the name of a profile. Home: Platform families, section 1, and Profiles, section 12.

Control plane

The part of the construction platform that runs outside the isolation boundary and performs stage S10: it generates the attestations and signatures from the build record. Home: Construction Constitution, SCF-ART-009, and Platform families, SCF-PLT-006.

Artefact

A file produced by a build: an image, a root filesystem, a package set, a manifest or a report. Home: Construction Constitution, group SCF-ART.

Manifest

The machine-readable description of what a build produced. Home: Construction Constitution, SCF-ART-001.

Bill of materials

The machine-readable list of the components of a release, each with identity, version, digest, licence and supplier. Home: Construction Constitution, SCF-ART-002.

Attestation

Signed evidence about how an artefact was produced. A provenance attestation describes the build platform, the lock and the inputs. Home: Construction Constitution, SCF-ART-003.

Trust anchor

A key, certificate or digest accepted without further proof, as the basis for authenticating an input. Home: Construction Constitution, SCF-SRC-003.

Publication route

A means by which a producer makes something available to recipients, such as a website, a repository or a registry. Two routes are independent when they share no administrator credential. Home: Construction Constitution, SCF-ART-010.

Producer-held snapshot

The immutable snapshot of the inputs a build consumed that the producer keeps itself on a platform that provides no archive service. In practice it is a content-addressed mirror of exactly the inputs a lock consumed. Home: Construction Constitution, SCF-SRC-004.

Clean environment

An environment that holds nothing of any earlier build of the release, so that a rebuild depends only on the lock, or on the export of the specification and the lock, and on the origins they name. Home: Construction Constitution, SCF-REP-001.

Independent rebuild

A rebuild of a release from its lock that runs on a different host, under a different builder identity, with no cache or output of the original build and no administrator credential in common with it, and whose result is compared with the release. Home: Construction Constitution, SCF-REP-002 and SCF-REP-004.

Reference profile

The profile that is chosen to stand for a platform family in the independent rebuild, at least one per family the producer builds on. Home: Construction Constitution, SCF-REP-004.

Platform family

A group of systems that share a packaging ecosystem and a tooling model, such as deb, rpm, apk, BSD pkg, IPS, ports or source-built systems. Home: Platform families.

Source-first

Of a platform family: a release is built from one source tree as a single unit, and packages are a way of slicing the result, as opposed to a system composed from pre-built packages. Stage S4 builds the toolchain for such a system. Home: Platform families, section 2; the platform facts are in the Platform dossiers.

Adapter

The component that maps the portable build model onto one platform family. Home: Platform families.

Portable entity

One of the entities of the portable model — origin, pin, component, selection, closure, overlay, hook, layout, boot set, installer contract, manifest, attestation — that every adapter maps onto its platform. Home: Platform families, section 3.

Privilege class

The privilege an adapter declares it needs, as one of its capabilities. It decides which class of worker, a worker being classed by the privilege it provides, can run the adapter. Home: Platform families, SCF-PLT-009.

Platform key

The key in the firmware of a machine that authorises changes to the keys the firmware trusts to start software. A producer whose boot chain depends on it enrols its own. The facts about named firmware are in the Platform dossiers. Home: Platform families, SCF-PLT-024.

Metadata service

A service of a hosting environment, reachable from inside an instance, that supplies the instance with its configuration and credentials. Home: Construction Constitution, SCF-BLD-013, for the build side, and Profiles, SCF-IMG-003, for a base image.

Installed surface

Everything a system installs and thereby exposes: the packages and files in the image, the services and the interfaces they open. Home: Construction Constitution, SCF-ISO-001, and Profiles, SCF-IMG-007, for the report per release.

Security defaults

The settings of a system as delivered that bear on its security, such as the firewall, the access control, the update policy and the credential settings. Home: Construction Constitution, SCF-GOV-005, and Profiles, SCF-WLB-008.

Mark

A name, logo or other element of visual identity that an upstream project or a producer reserves under its trademark terms. Home: Construction Constitution, SCF-LGL-004, and Profiles, SCF-WLB-002.

Free text

A value of a specification field that is not limited to a fixed set of permitted values and is written by a person or taken from outside the specification. Home: Construction Constitution, SCF-SPC-010.

Metadata source

Any place from which an instance takes its configuration or identity when it starts, a metadata service being one. Home: Profiles, SCF-IMG-004.

Construction pipeline

The ten stages S1 to S10 and the two verification gates V1 and V2 through which every specification passes. Home: Platform families, section 2.

Image-first and installer-first

An installer-first system is assembled on the target by an installer from packages or sets. An image-first system is delivered as a prepared image that is written to the target. Home: Platform families, SCF-PLT-008.

Release and service

Release

An immutable, signed set of artefacts of a product, with a manifest, evidence and a support statement. A release of SCF itself is an SCF release. Home: Construction Constitution, SCF-ART-005.

Release version

The human version of a release, as against its machine identities, in the form that section 3 of Update and lifecycle sets out. It describes a product built with SCF and is not the version of SCF itself, whose classes are those of the Change policy. Home: Update and lifecycle, section 3.

Channel

A named line of releases that clients follow to receive updates. A channel points at immutable releases and their corrections; the pointer moves, the releases do not. Home: Update and lifecycle, section 5, with SCF-LCM-002 for what every channel has.

Suite

The name under which a channel is published in repository metadata, such as <release>-security. Home: Update and lifecycle, section 5.

Function level

The MAJOR.MINOR pair of a release version. Releases that share it differ only by fixpack. Home: Update and lifecycle, section 4.

Fixpack

A release that raises only the FIX component of the release version. Its content and whether it is cumulative are matters for the rules of section 4. Home: Update and lifecycle, section 4.

Advisory

A published notice that accompanies a correction: security, defect or enhancement. Home: Update and lifecycle, section 6.

Defect record

The record opened when a defect is accepted, before a correction exists. It is separate from the advisory that later corrects the defect. Home: Update and lifecycle, section 6.

Security update

An update that corrects a vulnerability and is announced by a security advisory. Home: Construction Constitution, SCF-UPD-003, and Update and lifecycle, section 5.1.

Known-exploited vulnerability

A vulnerability that is listed in the CISA Known Exploited Vulnerabilities Catalog or in a feed of exploited vulnerabilities that the producer names in the release record. Home: Construction Constitution, SCF-VUL-003.

Disclosure policy

The producer’s published statement of how reports of vulnerabilities are received and handled: the expected response times and the disclosure process. Home: Construction Constitution, SCF-VUL-007.

Support period

The period during which the producer commits to supply corrections, ending on the end-of-support date. Home: Construction Constitution, SCF-GOV-004, and Update and lifecycle, section 7, which sets out its phases.

General availability

The first publication of a release to recipients in general: its first promotion into the release suite after the release gate. A candidate that carries a pre-release qualifier, or that sits in the beta or <release>-proposed suite, is not generally available. Home: Update and lifecycle, section 5, and SCF-ULC-019.

Delivery surface

The place at which a recipient obtains a release and what goes with it: a download page, a repository, a registry or a medium. Home: Construction Constitution, SCF-ART-006 and SCF-ART-007.

Release documentation

The documents delivered or published with a release that describe the release as delivered, among them the installation guide, the handover documentation, the list of exposed services and the list of network endpoints. It is not the release record. Home: Construction Constitution, SCF-ISO-002, SCF-PRV-001 and SCF-HUM-008.

Update contract

What a producer declares about how a release is updated: the channel it follows, the cadence of corrections, how an update is verified and how it is rolled back. Home: Construction Constitution, SCF-HUM-008, and Update and lifecycle, SCF-ULC-005.

Deployment

In an atomic or image-based system, the complete bootable content of the system volume that can be selected at boot: an image written to a slot, or a committed tree checked out beside the running one. It is the unit of update, and the release is the deployment. The word keeps its everyday meaning, the setting in which a system is used, in “intended deployment context” (SCF-GOV-001) and in the name of the profile Regulated and air-gapped deployment. Home: Update and lifecycle, section 9, and Profiles, section 7.

Staged activation

An update method in which a new version is first written and verified beside the running one and then made the version selected at the next boot, the previous version remaining available to return to. Home: Construction Constitution, SCF-UPD-009, and Update and lifecycle, SCF-ULC-048.

Demotion

A channel ceasing to point at a release. The release itself is not altered (SCF-ART-005), and it may still be obtained by its identity. Home: Update and lifecycle, section 5.

Known-good state

The state of a system before an update, to which a rollback returns it and in which it works as before. Home: Construction Constitution, SCF-UPD-006.

Reference installation

An installation of a stated release that serves as the starting point of a test of an update. Home: Update and lifecycle, SCF-ULC-007.

Recovery path

The documented way to bring a system back into service, or to regain access to what it protects, when the primary system does not start or cannot unlock. Home: Construction Constitution, SCF-OPS-003.

Withdrawal

The end of the force of a rule, or of the offer of a release through a suite, without erasing it. A withdrawn rule stays in its document as a stub that keeps its identifier; a withdrawn release is dropped from the suite that offered it, and the release itself is not altered. Home: Change policy, SCF-CHG-010 and SCF-CHG-013, and Update and lifecycle, SCF-ULC-019.

Governance

Threat model

The written statement of a system’s assets, the adversary capabilities in scope, the trust boundaries and the risks accepted out of scope. Home: Construction Constitution, SCF-GOV-003.

Profile

A class of system that adds requirements to the Constitution, such as desktop, server, appliance or kiosk. A profile is not a document about one release; that is a conformance statement. The profiles of HIF belong to HIF; where SCF names one it says “HIF profile”. Home: Profiles.

Invariant

A property that a profile declares to hold under every permitted variation of it. Home: Profiles.

Exception

A registered, bounded, owned and dated deviation from a requirement. Home: Construction Constitution, SCF-GOV-007.

Exception register

The list of the exceptions of one release, each with the fields of SCF-GOV-007 and of the exception record of SCF-EVL-018. Home: Evaluation and conformance, section 8.

Security posture

The security-relevant state of a release as delivered: the defaults it ships with, the choices it presents at first use (storage encryption, account credentials, automatic updates and telemetry) and the exceptions registered for it. Home: Construction Constitution, SCF-HUM-003 and SCF-HUM-008.

Provisioning contract

The declared means by which the party that deploys an image-first system sets its first-boot choices, in the place of a first-run screen. Home: Construction Constitution, SCF-HUM-003.

Any screen, dialog, prompt or setting through which a system asks a person to give or to refuse consent, for example to telemetry or to a report. Home: Construction Constitution, SCF-HUM-004.

Plausible time

A time that is not earlier than the release date and not later than the bound the profile states. Home: Construction Constitution, SCF-HWE-011.

Compliance baseline

A published set of controls with a revision, and with levels where the set has them, against which a system is measured; a product names it with its exact revision. The regimes of the profile Regulated and air-gapped deployment use it, and the kernel hardening baseline of SCF-ISO-005 is one of the same kind. “Baseline verification corpus” below is a different thing. Home: Profiles, SCF-REG-001.

Public session

The session in which a kiosk is used by the public in its fixed role. Home: Profiles, SCF-KSK-008.

Maintenance path

The way by which authorised staff enter a kiosk to administer it, with an account, a session and an entry point of its own, apart from the public session. Home: Profiles, SCF-KSK-004 and SCF-KSK-005.

Evidence and conformance

Evidence

A retained record that shows a requirement is met, produced at one of the evidence levels E1 to E5; a declaration alone, level E0, is not evidence. Home: Evaluation and conformance, section 2.

Evidence level

The rung, E0 to E5, at which a property was observed. Home: Evaluation and conformance, section 2.

Reference hardware

The machines, each identified by make, model and firmware version, on which reference-hardware (E4) evidence is produced. A conformance statement names them. Home: Evaluation and conformance, section 2 and SCF-EVL-014.

Reference device

One machine of the reference hardware, identified by make, model and firmware version, and listed as such in the hardware matrix. Home: Construction Constitution, SCF-HWE-001.

Hardware matrix

The published list of the architectures, platforms and reference devices a release is supported on. Each entry carries exactly one of three labels: supported, which means the producer states that it supports the entry; tested, which means a verification record exists on that device; and untested, which means neither is claimed. Home: Construction Constitution, SCF-HWE-001.

Baseline verification corpus

The checks that SCF itself supplies for the requirements it can verify, each run at its required evidence level. Home: Evaluation and conformance, section 3.

Applicable

Of a rule: applicable to a release unless the condition in its Applies line is false for the release. Of a check of the baseline: applicable when at least one rule it verifies is applicable. Home: Evaluation and conformance, SCF-EVL-009 and SCF-EVL-010.

Finding

A recorded result of a check, review or test showing that a required or claimed property does not hold or is in doubt. A finding carries a severity class; the findings log lists them. The severity scale of advisories is a separate scale. Home: Evaluation and conformance, SCF-EVL-008; the scale of advisories is SCF-ULC-030 of Update and lifecycle.

Build escape-attempt corpus

The one set of attempts, defined in Evaluation and conformance, section 3.11, by which the boundary of a build is tested: host-path mounts, device access, a shared-kernel exploit class, network reach to the control plane and to metadata services, and access to another build. Home: Construction Constitution, SCF-BLD-002 and SCF-BLD-010.

Traceability matrix

The chain from an obligation through a requirement, an implementation and a check to evidence and exceptions. Home: Evaluation and conformance, section 6.

Release gate

The twelve steps that precede the signing of a release. Home: Evaluation and conformance, section 7.

Release record

The controlled record of one release: its inputs, evidence, exceptions and approval. It says what was done to earn a claim. Home: Release record template.

Conformance level

One of SCF-Declared, SCF-Conformant and SCF-Validated. Home: Evaluation and conformance, section 5.

Conformance statement

The statement, for one release, of the conformance level claimed, the bounds of the claim and what backs it: identification, scope, traceability, exceptions and approval. It names the SCF version, the profiles, the release, the architectures and the reference hardware. It replaces the term “product profile”. Home: Evaluation and conformance, section 5, and the Conformance statement template.