Logo
Cybersecurity

What CISOs Should Ask Before Choosing a Penetration Testing Provider in 2026

ITSEC Asia, Indonesia's leading cybersecurity company, breaks down the questions CISOs should ask before choosing a penetration testing provider in 2026, and why the answers matter more than the price on the quote.

ITSEC AsiaITSEC Asia
|
Jul 17, 2026
What CISOs Should Ask Before Choosing a Penetration Testing Provider in 2026

Introduction

What percentage of your last penetration test report was actually proven exploitable, and what percentage was a list of things a scanner flagged and nobody validated? Most CISOs cannot answer that question with confidence, and that is exactly the problem. Buyers guides published this year point to a pattern worth sitting with. If a quoted penetration test comes in at four to five thousand dollars or less, it is very likely an automated vulnerability scan wearing a pen test label, not manual work performed by a skilled tester. That gap between what is sold as a penetration test and what is actually delivered is why the selection conversation matters so much more than most procurement teams treat it. ITSEC Asia, Indonesia's leading cybersecurity company, works with organizations across Indonesia, Singapore, Australia, and the UAE that have gone through this exact evaluation, and the questions that separate a genuinely useful engagement from an expensive checkbox exercise are more specific than most RFPs ever ask.

Source: Six Questions to Ask a Penetration Testing Vendor

The Question That Actually Separates Real Testing From a Repackaged Scan

Before a CISO asks about cost or timeline, the first question worth asking is how much of the engagement is manual testing performed by a person, and how much is automated tooling running in the background. A provider who cannot answer that specifically, or who deflects to a list of tool names instead of describing what a tester actually does with those results, is usually scanner heavy underneath a nicer report template.

  • Scanners work by matching what they see against known signatures, so they catch outdated software versions or exposed endpoints reliably, but they cannot reason through a multi-step attack path the way a human attacker would, such as testing whether one authenticated user can quietly access another user's data.

  • A serious provider should be able to describe how their testers form a hypothesis about a weakness, chain it with another finding, and then attempt controlled exploitation to confirm the risk is real rather than theoretical.

  • Asking which specific testers will be assigned to the engagement, and what certifications they individually hold rather than a generic reference to a certified team, tends to reveal a lot in a single answer.

  • A company that is ISO 27001 certified at the corporate level does not guarantee that the individual assigned to a project can find a real SQL injection or a broken access control chain, and a provider confident in its people will name them without hesitation.

The gap between a scanner flagging an anomaly and a tester actually proving it exploitable is what decides whether a pentest report is genuinely actionable, or just a checklist that looks convincing on paper.

Source: Why Automated Scanners Miss Real Vulnerabilities · Autonomous AI Agents for Penetration Testing: A Complete Guide

What a Credible Provider Should Be Able to Prove

Once methodology is settled, the conversation should move to proof rather than promises. A useful test is to request a sample report before signing anything, since the report format reveals more about testing quality than any sales call ever will.

  • A strong sample includes proof of concept evidence for every finding, screenshots showing the access that was actually achieved, and a clear narrative of how findings were chained into a realistic attack path rather than a flat list graded by a generic severity score.

  • Scoping is another area where the answers diverge sharply between serious providers and price generators; a quote produced without a short scoping call, one that asks how many applications, user roles, and APIs are actually in play, is essentially a guess.

  • A quote without proper scoping usually means either the provider is padding for unknowns, or a change request is coming midway through the engagement.

  • It is worth asking directly what happens between report delivery and retesting, since quality providers typically build in thirty to ninety days of remediation support, while a red flag looks like a report sent by email with no debrief and no path back to the tester who found the issue.

None of these questions require deep technical fluency to ask, they simply require treating the evaluation as a scorecard applied consistently across every provider on the shortlist, rather than trusting the reassurance printed on a homepage.

Source: 10 Questions to Ask Before Hiring a Penetration Testing Provider · Six Questions to Ask a Penetration Testing Vendor

Why This Decision Carries More Weight in Indonesia's Compliance Climate

For organizations operating in Indonesia, this selection process is no longer just good practice, it sits inside a tightening regulatory picture. UU PDP, the country's Personal Data Protection Law, has moved past its transition period and now carries real enforcement exposure, and its provisions expect organizations to regularly identify and remediate vulnerabilities rather than treat a security assessment as an annual formality. Sector regulators add another layer on top of that baseline, with OJK requiring scenario based cybersecurity testing at least annually for commercial banks, and expecting audit grade evidence of testing from payment system and digital financial asset providers. Indonesia's exposure is also simply larger than it used to be, with internet users climbing from roughly 221.6 million in 2024 to about 229.4 million in 2025 according to APJII, which widens the attack surface every regulator and board member is now asking questions about. Choosing a provider who can produce audit ready, timestamped documentation of what was found and what was actually fixed is quickly becoming the difference between passing a regulatory review and scrambling to explain a gap in evidence after the fact.

Source: Top Penetration Testing Companies in Indonesia 2026 · From Policy to Practice: How Indonesia's UU PDP 2022 Shapes Cybersecurity Readiness in 2025

Choose the Provider Whose Answers You Can Verify

The right penetration testing provider is not the one with the most confident sales pitch, it is the one whose claims about methodology, testers, and validation hold up when you actually check them. ITSEC Asia has spent more than a decade working alongside organizations across Indonesia, Singapore, Australia, and the UAE on exactly this kind of evaluation, and Bronyx, ITSEC Asia's AI powered continuous penetration testing platform, was built around the same principle this article keeps circling back to: findings should be validated before they are reported, not after a client asks why an incident happened despite a clean scan.

Visit bronyx.ai to see how continuous, AI-powered penetration testing works, or reach the ITSEC Asia team directly at itsec.asia/contact to talk through what a real evaluation should look like for your organization.

Share this post

You may also like

Cybersecurity Job Titles Don't Tell the Whole Story
Cybersecurity

Cybersecurity Job Titles Don't Tell the Whole Story

Two candidates apply for the same security analyst position. Both have relevant qualifications and list incident response among their skills. One can investigate an alert, correlate logs and explain when an incident needs escalation. The other understands the theory but has limited practical experience. On paper, they may look similar. At work, they will need different levels of supervision. This is a challenge for cybersecurity workforce planning. Job titles and qualifications help describe a candidate's background, but employers also need a reliable way to assess practical capability and identify what someone must learn before taking on greater responsibility. ENISA's European Cybersecurity Skills Framework provides a useful reference. Its 12 cybersecurity role profiles describe the responsibilities, skills, knowledge and competencies associated with different professional roles. ENISA is currently revising the framework to reflect developments such as AI and secure digital product lifecycles, with new proficiency levels planned to support clearer skills definitions, career pathways and workforce assessment. These issues will be discussed at its conference on 4–5 November 2026. ENISA [https://www.enisa.europa.eu/events/european-cybersecurity-skills-conference-2026?utm_source=chatgpt.com] The principle applies

ITSEC AsiaITSEC Asia
|
Okt 26, 2026 — 4 minutes read
Teaching People to Use AI Without Security Is Half a Lesson
Cybersecurity

Teaching People to Use AI Without Security Is Half a Lesson

Seven hundred and fifty government employees across Kalimantan started AI training this week. The program, run by BLSDM Komdigi Banjarmasin with ASEAN Foundation, covers AI fundamentals, ethics, implementation and something that deserves to sit comfortably beside all three: data security. That combination makes sense. Organizations are teaching more people how to use AI because AI is becoming part of ordinary work. Employees can summarize documents, analyse information, draft material and automate routine tasks without writing a line of code. Every new capability also creates a new question: what exactly are we giving the AI? THE AI SKILL GAP HAS A SECURITY SIDE An employee can be perfectly competent at prompting an AI system while making poor security decisions around it. Imagine someone needs to summarize a lengthy internal report. Uploading the document may produce an excellent summary. Whether the document should have been uploaded in the first place is an entirely different test. As AI becomes commonplace, workers need enough security literacy to ask questions such as: * What information am I

ITSEC AsiaITSEC Asia
|
Sep 08, 2026 — 3 minutes read
How Continuous Pentesting Supports PCI DSS Compliance
Cybersecurity

How Continuous Pentesting Supports PCI DSS Compliance

Organizations that process, store or transmit payment card information face increasing pressure to protect sensitive data and comply with industry standards. Among the most widely recognized requirements is the Payment Card Industry Data Security Standard (PCI DSS). While many organizations view PCI DSS as a compliance exercise, the reality is that the framework is designed to strengthen security and reduce the risk of data breaches. As cyber threats continue to evolve, organizations are also recognizing that point-in-time assessments may no longer provide sufficient visibility. This is where Continuous Pentesting and Continuous Security Validation can help. WHAT IS PCI DSS? PCI DSS is a security framework developed to help organizations protect cardholder data and maintain secure payment environments. It applies to merchants, financial institutions, payment processors and service providers that handle payment card information. The standard covers multiple areas, including: * Network security. * Access control. * Vulnerability management. * Monitoring and logging. * Security testing. * Incident response. The objective is not simply compliance but the protection of sensitive payment information. WHY PENETRATION TESTING

ITSEC AsiaITSEC Asia
|
Jun 15, 2026 — 4 minutes read

Receive weekly
updates on new posts

Subscribe