Glossary
Terms used throughout the SPEKTRA Edge OS guide.
- Attestation
- The process by which a device proves its identity and reports its integrity to the platform using its TPM, before receiving credentials. See TPM & device attestation.
- Configuration storage
- The persistent area that holds device settings, identity, the administrator password, and hooks. Survives reboots and OS upgrades. See how persistence works.
- Data area
- The persistent area that holds container images, workload data, and logs. Uses most of the disk. See Storage.
- Device type
- The combination of hardware family and CPU architecture that identifies a platform and determines image compatibility. See supported platforms.
- Disk encryption
- Encryption of the configuration and data areas at rest, unlocked automatically by the TPM. See Disk encryption.
- Hook
- A user-provided script run at a defined lifecycle point (boot, after the agent starts, or shutdown). See Boot & shutdown hooks.
- Onboarding / provisioning
- How a device obtains an identity and joins a project — via zero-touch provisioning, a provisioning policy, or pre-registered hardware. See Device setup & provisioning.
- Provisioning policy
- A rule that lets devices self-register into a project from a template, either unattended or with manual approval. See onboarding methods.
- Recovery passphrase
- A human-known break-glass passphrase that can unlock an encrypted device when automatic unlock is unavailable. See Disk encryption.
- Secure Boot
- A firmware feature that allows only signed, trusted boot software to run. See Secure Boot.
- System image
- The read-only operating system a device boots from. Replaced as a unit during upgrades; not meant to be modified in place. See how persistence works.
- TPM (Trusted Platform Module)
- A hardware security module that provides device identity and protects keys, including the keys used for disk unlock. See TPM & device attestation.
- Zero-touch provisioning
- Onboarding in which unconfigured hardware automatically finds the platform, proves its identity, and receives credentials with no per-device setup. See onboarding methods.