Esc
Source Code Hardening
Definition
Hardening source code with the intention of making it more difficult to exploit and less error prone.
Artifact Relationships:
This defensive technique is related to specific artifacts. Click the artifact node for more information.
Technique Subclasses
There are 12 techniques in this category, Source Code Hardening.
| Name | ID | Definition | Synonyms |
|---|---|---|---|
| Source Code Hardening | D3-SCH | Hardening source code with the intention of making it more difficult to exploit and less error prone. | |
| - Memory Block Start Validation | D3-MBSV | Ensuring that a pointer accurately references the beginning of a designated memory block. | |
| - Pointer Validation | D3-PV | Ensuring that a pointer variable has the required properties for use. | |
| - Domain Logic Validation | D3-DLV | Validation of variable state in the context of the domain application. | |
| - Operational Logic Validation | D3-OLV | Validation of variable state in the context of the control logic of the operational application. | |
| - Null Pointer Checking | D3-NPC | Checking if a pointer is NULL. | Nil Pointer Checking |
| - Variable Type Validation | D3-VTV | Ensuring that a variable has the correct type. | |
| - Variable Initialization | D3-VI | Setting variables to a known value before use. | |
| - Integer Range Validation | D3-IRV | Ensuring that an integer is within a valid range. | |
| - Credential Scrubbing | D3-CS | The systematic removal of hard-coded credentials from source code to prevent accidental exposure and unauthorized access. | |
| - Reference Nullification | D3-RN | Invalidating all pointers that reference a specific memory block, ensuring that the block cannot be accessed or modified after deallocation. | |
| - Trusted Library | D3-TL | A trusted library is a collection of pre-verified and secure code modules or components that are used within software applications to perform specific functions. These libraries are considered reliable and have been vetted for security vulnerabilities, ensuring they do not introduce risks into the application. |