How to prepare for a VAPT: a checklist for Philippine IT teams
What to decide, gather and tell your team before a vulnerability assessment and penetration test, so testing runs smoothly and the report is useful.
Why preparation matters
A vulnerability assessment and penetration test (VAPT) checks your systems the way an attacker would. Testers can only check what you put in scope, and the report is only as useful as the decisions you make before testing starts. A few hours of preparation saves days of back-and-forth and gives you findings you can act on.
1. Decide what you want to test
List the systems that matter most: public websites, web applications, APIs, internal networks, cloud environments and mobile apps. For each one, write down the URLs, IP ranges or app versions. If you are not sure where to start, begin with anything that is reachable from the internet or holds personal data.
2. Choose production or staging
Testing production shows your real exposure but carries some risk of disruption. Testing staging is safer, but only useful if it closely matches production. Many teams test staging for intrusive checks and production for external exposure. Agree on this before testing starts.
3. Agree on testing windows and rules of engagement
Set the dates and hours when testing may happen, who to call if something breaks, and which actions are off-limits, such as denial-of-service tests or changes to live data. Put this in writing and get sign-off from management. Written permission protects both your team and the testers.
4. Prepare accounts and access
Testing with a signed-in account finds issues that testing from the outside cannot reach. Create test accounts for each user role in your applications, and remove them when testing ends. If testers need VPN or on-site access for internal networks, arrange it in advance.
5. Tell the right people
Let your IT operations team, helpdesk and any outside providers, such as hosting, cloud or managed security, know that testing is planned. Some providers require advance notice before anyone tests systems they host. Decide whether your monitoring team should be told, or whether you also want to see if they notice the activity.
6. Back up and freeze changes
Make sure recent backups exist for every system in scope. Avoid major releases during the testing window so the findings reflect a stable version.
7. Know what you need the report for
If you are preparing for the Data Privacy Act of 2012, ISO/IEC 27001 or PCI DSS, mention it during scoping. The testers can then organize findings around what those reviews look at, which makes the report easier to use.
8. Plan for fixing and retesting
A VAPT is only useful if the findings get fixed. Set aside time for your developers and system administrators after the report arrives, and agree on who owns each fix. Then retest to confirm the fixes work.
How B1G2 runs a VAPT
B1G2 combines automated scanning with manual testing by our security team, so we confirm what is really exploitable and filter out false positives. You get a report with risk-rated findings and practical fixes, a walkthrough session with your team, and a free retest using KinoSec autonomous pentesting once you have fixed the findings.
You do not need everything on this list to ask for a quote. Send us what you have, even just your name and email, and we will help you scope the rest. Use our contact form and choose VAPT, or call +63 915 341 0480.