Penetration Testing Services in Taiwan

Black-box, white-box, and grey-box penetration tests simulating real attack chains, by a team whose members hold OSCP. Remediation report and retest included.

Testing Approaches & Scope

Depending on your network architecture and the access you provide, penetration testing is conducted using three approaches:

  • Black-box testing: Our team simulates an external attacker's perspective with no prior accounts or architecture information, attacking from the public internet.
  • Grey-box testing: You provide limited access — for example, a VPN connection into an internal network that isn't publicly reachable — simulating an attacker who has already gained an initial foothold. This approach covers deeper risks more efficiently.
  • White-box testing: Our team receives full architecture documentation, source code, or system credentials for the most comprehensive vulnerability assessment.

Beyond network-level testing, we also offer API penetration testing, assessing externally exposed APIs for authentication bypass, broken access control, and data exposure risks, which can be conducted under any of the access models above.

Penetration Testing Process

Professional penetration testing process conducted by a team whose members hold OSCP

Our penetration testing methodology combines the Penetration Testing Execution Standard (PTES) and the OWASP Testing Guide, covering the complete process from scope definition through to final reporting, with test steps and evidence retained in the report so results can be reproduced and verified.

  1. Scope Definition:Define test scope, target systems, and methodology together with your team.
  2. Information Gathering:Collect target intelligence using passive and active reconnaissance.
  3. Vulnerability Scanning:Use automated tools to discover and classify vulnerabilities.
  4. Manual Testing:Perform in-depth manual exploitation and validation.
  5. Report and Recommendations:Provide a detailed report with findings, impact, and remediation guidance.

Regulatory and Standards Mapping

Penetration test reports can serve as reference material for multiple regulatory and international standards: Taiwan's Cyber Security Management Act audits, ISO 27001:2022 risk assessments, PCI DSS annual testing requirements, and EU CRA technical documentation (see CRA Mapping Support, ISO 27001 Consulting).

Deliverables

Upon completion, you'll receive a comprehensive report including: an executive risk summary with business impact assessment for leadership, detailed technical findings with reproduction steps for your technical team, and remediation priorities ranked by risk level. One retest after remediation is included in the quote to verify vulnerabilities are properly fixed.

How is penetration testing priced?

ThunderShield's host and website penetration testing has public pricing, based on the number of targets. One IP address or one website hostname counts as one target; all paths and pages under the same hostname count as the same target, a different hostname (including subdomains) counts as another, and each additional target is charged at the same price. The price includes one initial test and one retest, and is quoted before tax. See the pricing page for current prices.

Frequently Asked Questions

What is penetration testing?

Penetration testing is a simulated cyberattack on your systems to identify exploitable vulnerabilities before real attackers do.

How often should penetration testing be performed?

Most organizations should conduct penetration testing at least annually, or after any major system change or security incident — consistent with PCI DSS §11.4.3 and NIST SP 800-115 guidance.

What is the difference between penetration testing and vulnerability scanning?

Vulnerability scanning is automated and identifies known weaknesses. Penetration testing is manual and actively attempts to exploit those weaknesses to assess real-world impact.

Can penetration test reports serve as reference for CRA mapping?

Yes, for reference. CRA Annex I Part II item 3 requires effective and regular security testing of the product, and our reports can be delivered in the Annex VII item 6 format as a reference for the testing records in your technical documentation.

Will penetration testing disrupt production systems?

We confirm scope, timing, and off-limits actions with you beforehand, and avoid techniques that could cause service disruption (such as denial-of-service attacks). Higher-risk verification steps require your prior consent and can be scheduled during off-peak hours or against a test environment to minimize impact on production.

How long until I receive the report?

Timing depends on project scope and testing scope. We'll confirm the exact delivery timeline with you before the project begins — please raise any timing requirements during consultation.

Is retesting an extra cost?

No. After remediation, one retest is included in the quote to verify that reported vulnerabilities have been properly fixed. The scope of the retest follows the project agreement; additional retest rounds or expanded scope can be arranged on request.

How is penetration testing priced?

ThunderShield's host and website penetration testing has public pricing, based on the number of targets. One IP address or one website hostname counts as one target; all paths and pages under the same hostname count as the same target, a different hostname (including subdomains) counts as another, and each additional target is charged at the same price. The price includes one initial test and one retest, and is quoted before tax. See the pricing page for current prices.

Contact ThunderShield for a consultation · View pricing plans