Day-to-Day Responsibilities
Agree the scope, targets, rules and timing with the client in writing before any testing begins.
Gather information about target systems, such as domains, IP ranges and exposed services (reconnaissance).
Scan networks, web applications and APIs for misconfigurations, outdated software and weak access controls.
Try to exploit confirmed weaknesses in a safe, controlled way to see how far a real attacker could go.
Test how people and processes respond, such as phishing awareness, where the client has agreed to this.
Write a clear report with severity ratings, proof of impact and step-by-step fixes for developers and system administrators.
Retest systems after fixes are made and brief management and technical teams on the findings.


