Appendix B: Glossary
In projects, tenders and interviews you meet the same concepts under different names, as acronyms or as spelled-out terms. This glossary sorts the terms alphabetically. Where the lab outputs and data in this book show a German word for a term, it follows in parentheses.
Tip: In an interview, it comes across as confident if you know both the short and the long form and briefly connect them once, for example: “the SBOM, that is, the software bill of materials”.
Glossary from A to Z
A
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Admission Control | – | Kubernetes mechanism that checks resources before they are stored and can reject or modify them. |
| Air Gap | – | Network that is completely separated from the internet, physically or logically. |
| Approval (Freigabe) | Release | Documented decision that an artifact may move on to the next zone or environment. |
| Artifact | – | Result of a build, such as a container image, a package or an SBOM. |
| Attestation | – | Signed statement about an artifact, such as “this SBOM belongs to this digest”. |
| Audit Mode | – | Mode in which a rule logs violations but does not block them. |
| Auditability | – | The property that every decision can later be traced and proven. |
B
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Base Image (Basis-Image) | – | Image on which your own image is built, such as
python:3.12-slim. |
| Build Environment | – | Machine, container or runner in which the build takes place. |
C
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Certificate | – | Binding of a public key to an identity, signed by a CA. |
| Certificate Signing Request | CSR | Request containing a public key that a CA is asked to sign. |
| Certificate Revocation List | CRL | List of certificates that were declared invalid before they expired. |
| Chain of Trust | – | Sequence of certificates from the root to the leaf that vouch for one another. |
| Checksum (Prüfsumme) | Hash | Short fingerprint of a file that changes with every modification. |
| Controlled Transfer | – | Regulated path on which artifacts cross a zone boundary after being checked. |
| Credentials | – | User name, password, token or key that you use to log in. |
| CVE | Common Vulnerabilities and Exposures | Public, unique identifier of a known vulnerability, such as CVE-2023-32681. |
| CVSS | Common Vulnerability Scoring System | Scoring system from 0 to 10 that rates the technical severity of a vulnerability. |
| CycloneDX | – | SBOM format from the OWASP Foundation with a focus on security data. |
D
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Dependency | – | Third-party library or component that your software needs to build or run. |
| Dependency Confusion | – | Attack in which a public package with the name of an internal package is installed in preference to it. |
| Desired State | – | Target state described in Git that GitOps tools establish. |
| Digest | – | Checksum (usually SHA-256) that identifies an image uniquely and immutably. |
| Drift | – | Deviation of the actual state in the cluster from the desired state in Git. |
E
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Enforcement | – | Mode in which a rule blocks violations instead of only reporting them. |
| EPSS | Exploit Prediction Scoring System | Probability that a vulnerability will be exploited in the next 30 days. |
| Exception (Ausnahme) | Waiver | Justified, time-limited and approved deviation from a rule. |
F
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| False Positive | – | Finding that a tool reports but that is not actually a problem. |
| Four-Eyes Principle | – | Rule that critical steps must be confirmed by two people. |
G
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| GitOps | – | Operating model in which Git is the single source of truth for deployments. |
| Grace Period (Frist) | Transition period | Period in which a new rule only warns before it is enforced. |
H
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Hardening | – | Reducing the attack surface, for example with non-root users and minimal images. |
| HSM | Hardware Security Module | Device that stores keys securely and never releases them in plain text. |
I
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| IaC | Infrastructure as Code | Describing infrastructure in versioned files instead of by hand. |
| Immutability | – | The property that a published artifact is never overwritten. |
| Ingestion | – | Taking an artifact into a system, such as an SBOM into Dependency-Track. |
| Intermediate CA | – | Subordinate certificate authority that does the everyday signing so that the root can stay offline. |
L
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Lease | – | Time-limited allocation of dynamic credentials in Vault or OpenBao. |
| License Compliance | – | Checking whether the licenses of all dependencies fit the intended use. |
M
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Manifest | – | Description of an image or a Kubernetes resource in JSON or YAML. |
| Mirror (Spiegel) | Proxy Repository | Internal copy of external package and image sources. |
| Multi-stage Build | – | Dockerfile with several stages so that build tools do not end up in the final image. |
O
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| OCI | Open Container Initiative | Standard for the image format and registry protocol that all common tools use. |
| Offline Signing | – | Signing without a connection to public services such as a transparency log or certificate service. |
P
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Pipeline | – | Automated sequence of steps such as building, checking, signing and delivering. |
| PKI | Public Key Infrastructure | The whole of certificate authorities, certificates, revocation lists and processes. |
| Policy as Code | – | Security and operations rules as versioned, testable code. |
| Provenance | – | Signed record of who built an artifact, when, where and from which source state. |
Q
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Quarantine (Quarantäne) | – | Isolated area in which artifacts wait until they have passed inspection. |
R
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Reachability | – | The question of whether vulnerable code is actually called by your application. |
| Recoverability | – | Ability to return to a secure state in an orderly way after an outage or compromise. |
| Referrer | – | OCI artifact, such as a signature or SBOM, that points to an image by digest. |
| Registry | – | Server that stores and delivers container images and other OCI artifacts. |
| Remediation (of a process) | Upgrading | Targeted improvement of an existing process until it meets the requirements. |
| Reproducible Build | – | Build that produces a bit-for-bit identical result from the same inputs. |
| Risk Acceptance | – | Documented decision by a responsible person to carry a known risk for a limited time. |
| Root CA | – | Top-level certificate authority, the trust anchor of your own PKI. |
| Rotation | – | Scheduled replacement of keys or credentials before they can be misused. |
| Runner | Agent | Process that actually executes pipeline jobs. |
S
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| SAST | Static Application Security Testing | Checking source code for vulnerabilities without running it. |
| SBOM | Software Bill of Materials | Machine-readable parts list of all components of a piece of software. |
| SCA | Software Composition Analysis | Checking dependencies for known vulnerabilities and licenses. |
| Secret | – | Confidential information such as a password, token or private key. |
| Short-lived Credentials | – | Credentials that automatically become invalid after minutes or hours. |
| Signature (Signatur) | – | Cryptographic proof that an artifact comes from a specific key and is unchanged. |
| Single Source of Truth | – | The one authoritative place for a piece of information, such as Git for deployments. |
| SLSA | Supply-chain Levels for Software Artifacts | Framework with levels for the security of the build process. |
| SPDX | Software Package Data Exchange | SBOM format from the Linux Foundation, standardized as ISO/IEC 5962. |
| Supply Chain | – | All steps and sources from the source code to the running software. |
T
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Threshold | – | Limit from which a finding stops the build or the approval. |
| Transparency Log | – | Public, append-only log of signatures, such as Rekor. |
| Triage | – | Reviewing, assessing and prioritizing findings by their actual risk. |
| Trust Anchor | – | Key or certificate that is trusted without further verification. |
| TTL | Time to Live | Period after which a token, lease or cache entry expires automatically. |
U
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Upstream | Source | Original location that packages or images come from, such as PyPI or Docker Hub. |
V
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| VEX | Vulnerability Exploitability eXchange | Machine-readable statement of whether a product is affected by a vulnerability. |
| Vulnerability | – | Flaw that attackers can exploit. |
Z
| Term | Long form / also | Explanation in one sentence |
|---|---|---|
| Zone | – | Network area with its own protection needs, such as internet, build or production. |
| Zone Boundary | – | Transition between two zones at which only checked data may pass. |