Glossary Code security terms, in plain words.
Short definitions of the terms you will meet in a scan report.
- CISA KEV
- The Known Exploited Vulnerabilities catalogue published by the US agency CISA: vulnerabilities that attackers are already using.
- CVE
- Common Vulnerabilities and Exposures. A public identifier, such as CVE-2024-3094, for one specific security flaw in one product.
- CVSS
- Common Vulnerability Scoring System. A score from 0 to 10 for how severe a vulnerability is, calculated from a vector that describes how it can be attacked and what the impact is.
- CWE
- Common Weakness Enumeration. A catalogue of kinds of software weakness, such as CWE-89 for SQL injection. A CVE is one flaw; a CWE is the type of flaw.
- Cyber Resilience Act
- Regulation (EU) 2024/2847. An EU law that sets cybersecurity requirements for products with digital elements, including an SBOM and vulnerability handling.
- DAST
- Dynamic application security testing. Testing a running application from the outside. scancodebase does static analysis, not DAST.
- EPSS
- Exploit Prediction Scoring System. An estimate of how likely a vulnerability is to be exploited in the near future.
- IaC
- Infrastructure as code. Files such as Terraform or Kubernetes manifests that describe infrastructure and can be scanned before they are applied.
- Lock file
- A file such as package-lock.json or poetry.lock that records the exact version of every dependency.
- NIS2
- Directive (EU) 2022/2555. An EU directive that requires essential and important entities to manage cybersecurity risk, including supply chain security.
- OWASP Top 10
- A widely used list of the most critical security risks for web applications, published by the OWASP Foundation.
- Reachability
- Whether vulnerable code can actually be executed from an entry point of the application. An unreachable vulnerability is far less urgent.
- SARIF
- Static Analysis Results Interchange Format. A standard JSON format for scanner results that GitHub, GitLab and Azure DevOps can display.
- SAST
- Static application security testing. Analysing source code for security flaws without running it.
- SBOM
- Software bill of materials. A machine-readable list of the components inside a piece of software, with versions and licences. Common formats are CycloneDX and SPDX.
- SCA
- Software composition analysis. Finding the open source components in your software and their known vulnerabilities and licences.
- Secret
- A credential that gives access to something: an API key, a token, a password or a private key.
- Software supply chain
- Everything that goes into your software that you did not write: base images, packages, build tools and the systems that deliver them.
- Source and sink
- The source is where untrusted data enters a program, such as a request parameter. The sink is where it can do damage, such as a database query.
- SQL injection
- A flaw where user input becomes part of a database query and changes what the query does. The fix is to pass values as parameters.
- SSRF
- Server-side request forgery. A flaw that lets an attacker make the server send requests to addresses the attacker chooses.
- Taint analysis
- Following data that comes from an untrusted source through the program to see whether it reaches a dangerous operation without being cleaned.
- VEX
- Vulnerability Exploitability eXchange. A document that states whether a product is affected by each known vulnerability in its components. Formats include OpenVEX, CycloneDX VEX and CSAF.
- XSS
- Cross-site scripting. A flaw where user input is shown in a web page as code, so an attacker can run scripts in another person's browser.