A software development and security testing model where one team builds the software, a second team tries to break it (find vulnerabilities), and the original team fixes them.

Objective:
A software development and security testing model where one team builds the software, a second team tries to break it (find vulnerabilities), and the original team fixes them.
How it’s used:
Pros
Cons
Categories:
Best for:
To read and compare several methodologies, we recommend the
> Extensive Methodologies Repository <
together with the 400+ other methodologies.
Your comments on this methodology or additional info are welcome on the comment section below ↓ , so as any engineering-related ideas or links.
(if date is unknown or not relevant, e.g. "fluid mechanics", a rounded estimation of its notable emergence is provided)
Full size images and downloads are only available, 100% free, for registered members.
> Login <