Skip to main content

26 guides, published by Security Brigade and last updated .

How the testing works

What a tester actually does, by asset class, and what tooling does and does not reach.

Scope and preparation

What to have ready, what can and cannot be tested, and how the boundary gets drawn.

Reading the report

Severity, CVSS and the vector string, and how to tell written work from tool output.

After the test

Sequencing the fixes, proving closure, and deciding when to test again.

Where the requirement comes from

Which regulators name you, and where the obligation arrives from when none do.

Buying one

What it costs, who is qualified to do it, and what you receive at the end.

Applying this to your own estate

Get a VAPT scoped against what you actually run.

Application count, environment, regulator and evidence deadline are what move a scope. A template does not know any of them. Describe your estate and you will get the scope, the cost and the retest cadence in writing. Security Brigade is CERT-In empanelled and publishes this site.