White hat and black hat describe permission and motive: one tests with consent to reduce risk, and the other acts without permission.
The labels are not a catalog of techniques, and this page does not explain how to break into systems.
How it works
White hat work stays inside a written scope, a time window, and targets the owner named.
Black hat work proceeds without that consent, for harm, theft, or profit.
Good intent does not expand a written scope by itself.
Touching customer data or a neighboring system you were not given is not authorized testing, even if the person claims they meant to help.
Concrete examples
- A company hires a tester to review its public site inside a written scope.
- A criminal enters a store system without permission to steal card data.
- An employee probes a production system they were never asked to test and causes an outage.
Protective measures
- Write scope, time window, and forbidden targets before any test begins.
- Give testers identities your team can recognize in logs.
- Treat access outside the written scope as an incident even if the person claims goodwill.
- Keep reports internal until the issues they describe are fixed.