1. Code vulnerabilities
Vulnerabilities are mistakes, errors or weaknesses in a piece of software’s source code that can be directly used by a hacker to perform an attack, such as gain access to a system or network.
When developing software, to ensure it is therefore essential to make sure the code is secure.
The planning stage is therefore crucial!

2. Best Practice Coding for Network Vulnerabilities
Programmers usually follow best practice coding principles.
Keep the code as simple as possible - complex designs increase the likelihood that errors will be made in their implementation, configuration, and use.
Conduct code reviews carried out by external testers. Internal testers or those developing the software may not spot bugs or security flaws.

3. Code Review
Think back to when we were carrying out our controlled assessment. Without knowing it, you were all code reviewers!

4. What is a code review?
A code review (sometimes referred to as peer review) involves one or several humans checking a program mainly by viewing and reading parts of its source code.
This process can be automated and carried out by a computer, but this is risky, as a computer may not pick up errors that may be apparent.
Code reviews should be carried out by people outside of a company or independent of that particular project.

5. Modular testing Think back (again) to your controlled assessment.
Modular testing involves checking individual subprograms or functions in a program.
Think back (again) to your controlled assessment.
We created our software using different functions. Before moving onto the next function we moved onto the next task or sub-problem, we tested our programs worked.
This is known as modular testing.
Just think – in many of your GCSE’s, you are tested in a modular way – to make sure you have understood a topic before moving onto the next.