Introduction Pseudo-random number generators (PRNGs) play a crucial role in modern cryptography and information security. These algorithms generate seemingly random sequences of numbers, which are essential for tasks like encryption, secure key generation, and digital signatures. PRNGs in the past have had many issues with predictability. Looking at the current and future research requires a look at how predictable the numbers really are. External Techniques Several techniques have arisen to generate random numbers, both on local machines and using real world chaos.

Introduction Prerequisites are incredibly important to any development project and was the OWASP Top 10, Number 4, Insecure Design. For the purpose of this document we will talk about it in context of security implications. This ended up being too big of a topic for just two posts, so here is part 3. In Pre Requisets Part 1, we looked at why pre-reqs are needed in general and how they apply to types of projects.

Introduction In this summation of “Code Complete 2” by Steve McConnell we will focus on variable naming and usage and how it ralates to security. Variable naming is an essential aspect of software development, and it plays a critical role in ensuring software security. Importance of Variable Naming Variable naming is important for software security because it helps to prevent common programming errors that can lead to security vulnerabilities. For example, if a variable is named incorrectly, it can be difficult to understand its purpose, which can lead to confusion and errors in the code.

Introduction Prerequisites are incredibly important to any development project and was the OWASP Top 10, Number 4, Insecure Design. For the purpose of this document we will talk about it in context of security implications. This ended up being too big of a topic for just one post, so here is part 2. In Pre Requisets Part 1, we looked at why pre-reqs are needed in general and how they apply to types of projects.

Introduction Prerequisites are incredibly important to any development project and was the OWASP Top 10, Number 4, Insecure Design. For the purpose of this document we will talk about it in context of security implications. Planning Comes First As the saying goes a failure to plan is a plan to fail. Without a solid foundation, similar to building a house, the entire program can fall. With no plan in place, code can end up being added in a half-hazard way, causing code paths to become unknown or unintentionally created.