The FREE Cybersecurity Glossary by Thor Pedersen!

Stack memory: A type of memory used by a computer's central processing unit (CPU) to store and manage data. It is used in computer programming to store temporary data and manage function calls. Examples include storing local variables and function parameters and managing the order in which functions are executed.

Static analysis: This involves reviewing the code of an application without executing it, aiming to discover potential vulnerabilities, bugs, or breaches of coding standards. This method focuses on the source code, byte code, or binary code, using a set of predefined rules or patterns to identify possible issues. It's particularly useful in identifying non-obvious errors, and unlike dynamic analysis, it can be conducted early in the development process.

Static Application Security Testing (SAST): A method of software testing in which the code is analyzed without executing it, with a focus on identifying potential security vulnerabilities. It is commonly used in software development. Examples include a static analysis tool that scans the code for potential security vulnerabilities or a static analysis tool that checks the code for adherence to security best practices.

Strongly typed programming languages: Languages that enforce strict rules for data types, requiring variables to be declared with a specific type and restricting operations to valid ones for that type. Examples include C, C++, and Java.

Structured programming: A paradigm of designing programs where the flow of control is governed by structured blocks, typically using sequences, selections, and loops. The main aim of structured programming is to enhance the clarity, quality, and development time of a computer program by making use of subroutines, loop control structures, and block structures. Its principles increase the maintainability and reliability of software, reducing the likelihood of bugs and vulnerabilities.

Synthetic transactions: Scripted actions that simulate user interactions with a system or application. These scripts mimic end-user behavior, such as logging in, navigating through an application, or completing a transaction, to proactively monitor and measure system performance and availability. Synthetic transactions are used in testing environments to identify potential issues before they impact end users, helping to maintain a high level of service availability and security.