Security Design

Spending more money does not guarantee better information security. Implementations must balance multiple priorities, including cost, ease of maintenance, scalability, and functionality. Appropriate planning, design, prototyping, and review eliminate the need for costly experimentation and the failure of projects to meet requirements. This process also catches security problems before they ever become part of the operational environment.

It is often the case that getting the security architecture of a project correct from the outset will negate many common security vulnerabilities before they can occur. It is a regular occurrence for organisations to be compromised by malware and hackers when the correct configuration and placement of the technical security products that are already in place (such as firewalls) would have avoided the problem entirely.

Unfortunately, the consideration of the security aspects of a project are often left to the eleventh-hour, or sometimes only after a project has gone live. This inevitably leads to a desperate attempt to back-engineer a level of security into a project as an after-thought; which can delay a project unexpectedly, or push it hopelessly over-budget.