Penetration Testing & Vulnerability Management

An authenticated web application scan may appear complete while the scanner has lost its session or never reached protected workflows. Findings can then omit important areas such as account settings or file upload functions. What to check Review authentication status, crawl and route coverage, session expiration, role permissions, excluded paths, and...

A firewall change can block a tested route without fixing the vulnerable service itself. A scanner may report the issue resolved from one network while the service remains reachable through another path. What to check Confirm the original finding, test vantage points, public and internal routes, firewall logs, and service exposure. Review whether...

An internet-facing system may have many scanner findings, but urgency depends on reachable attack paths, exploitability, data impact, and existing controls. Treating every finding equally can delay fixes that matter most. What to check Confirm asset ownership, exposure, vulnerable component, exploit availability, authentication requirements, business...

A rewritten application may remove old vulnerable code but introduce new routes or behavior. Closing findings based only on a different version number does not confirm the original weakness is gone. What to check Map the finding to the new route and component, reproduce the original test within authorized scope, and review changed authentication, input...

An application fix may reach the web interface while older mobile builds continue using a vulnerable API path. A server-side scanner alone may not reflect all client versions still in active use. What to check Inventory supported app versions and API routes, confirm the patch is enforced server-side where possible, and test authorized workflows across...

A development or diagnostic endpoint may remain accessible after its intended temporary use ends. Removing a link from the interface does not confirm that the route or API is no longer reachable. What to check Check authorized routes, DNS and host mappings, access logs, authentication, deployment configuration, and environment-specific feature flags....

A vulnerability may only be reachable under a particular role or permission combination. Retesting as an administrator can miss authorization flaws affecting ordinary users. What to check Identify affected roles, resources, and trust boundaries. Recreate authorized test accounts for each relevant role and verify both allowed and disallowed actions...

An API may expose multiple versions, deprecated routes, or alternate hostnames. Fixing the current endpoint does not close the weakness if an older version remains reachable. What to check Inventory versions and routes from code, gateway configuration, documentation, and traffic logs. Re-test the same authorized scenario across supported and legacy...