Model | Verification | Security Testing
The Security Testing practice leverages the fact that, while automated security testing is fast and scales well to numerous applications, in-depth testing based on good knowledge of an application and its business logic is often only possible via slower, manual expert security testing. Each stream therefore has one approach at is core.
The first stream focuses on establishing a common security baseline to automatically detect so-called “low hanging fruit”. Progressively customize the automated tests for each application and increase their frequency of execution to detect more bugs and regressions earlier, as close as possible to their inception. The more bugs the automated processes can detect, the more time experts have in which to use their knowledge and creativity to focus on more complex attack vectors and ensure in-depth appliation testing. As manual review is slow and hard to scale, reviewers prioritise testing components based on their risk, recent relevant changes, or upcoming major releases. Organisations can also access external expertise by participating in bug bounty programs for example.
Unlike the Requirements-driven testing practice which focuses on verifying that applications correctly implement their requirements, the goal of this practice is to uncover technical and business-logic weaknesses in application and make them visible to management and business stakeholders, irrespective of requirements.
|Maturity level||Stream AScalable Baseline||Stream BDeep Understanding|
|1||Perform security testing (both manual and tool based) to discover security defects.||Utilize automated security testing tools||Perform manual security testing of high-risk components|
|2||Make security testing during development more complete and efficient through automation complemented with regular manual security penetration tests.||Employ application-specific security testing automation||Conduct manual penetration testing|
|3||Embed security testing as part of the development and deployment processes.||Integrate automated security testing into the build and deploy process||Integrate security testing into development process|