FAQ
A centralized FAQ hub for all cybersecurity service pages.
Host Vulnerability Detection
- How is host vulnerability detection different from penetration testing?: Host vulnerability detection focuses on systematic scanning and validation to find known weaknesses and misconfigurations, while penetration testing simulates attacker behavior to validate exploitability and business impact.
- What host information is required before assessment?: You typically provide host inventory, IP ranges, OS versions, and maintenance windows. We help define a scoped plan that minimizes operational disruption.
- Will remediation guidance be included after the assessment?: Yes. The report includes risk levels, impacted assets, remediation priorities, and actionable fix recommendations for security and operations teams.
Web Vulnerability Detection
- Does web vulnerability detection cover OWASP Top 10 risks?: Yes. We systematically assess high-risk areas such as SQL injection, XSS, CSRF, and authentication/authorization weaknesses.
- Will testing affect production traffic?: Testing can be scheduled during low-traffic windows with controlled intensity and allowlist strategy to minimize impact on production systems.
- Do you provide retesting after fixes are applied?: Yes. We can perform retesting after remediation to verify vulnerabilities are effectively resolved and update risk status accordingly.
Secure Code Review (SAST)
- Is secure code review fully automated?: No. We combine SAST tooling with manual expert review to reduce blind spots and false positives from automation-only workflows.
- Which tech stacks and frameworks are supported?: Most common web and backend stacks can be assessed. We align review strategy to your language, framework, and dependency profile before starting.
- Will findings include remediation priority?: Yes. Each finding includes severity, impact context, remediation guidance, and a prioritized fixing order.
Penetration Testing
- 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 evidence for CRA mapping?: Yes. 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 to serve as testing evidence 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.
Website Stress Testing
- Is website stress testing the same as performance testing?: They are related but not identical. Stress testing focuses on stability under peak or extreme load, while performance testing broadly measures response time, throughput, and efficiency.
- Can stress testing be run against production?: Yes, with careful risk controls. In most cases we validate in staging first, then run controlled production tests with guardrails.
- Do results include optimization recommendations?: Yes. The report identifies bottlenecks, resource hotspots, and concrete optimization steps to improve availability and scalability.
Phishing Simulation Testing
- What is phishing simulation testing?: Phishing simulation testing sends controlled, realistic phishing emails to measure how employees identify and respond to social engineering attempts.
- Will phishing simulation disrupt daily operations?: No. Campaigns are planned to minimize disruption while still generating realistic behavior data for risk analysis and training.
- How are results used after the simulation?: Results are used to identify high-risk patterns, prioritize coaching, and build targeted security awareness programs for teams and individuals.
- How many drills should we run per year?: Article 30 of the Guidelines for Cyber Security Control of TWSE/TPEx Listed Companies requires at least one drill annually. Government agencies, under the Regulations on Reporting, Response and Drills for Cyber Security Incidents, run a social-engineering drill every six months. The market trend has shifted toward higher-frequency, smaller batches, which better mirror real attack cadence and reduce disruption from any single drill.
- Could the drill damage our reputation or trigger email filters?: We send drill emails from similar but distinguishable test domains and confirm allowlisting with your IT team beforehand, so the drill doesn't trigger spam filters or disrupt normal mail flow.
- Can the report be used directly as audit evidence?: Yes. The report includes an executive summary, a comparison against the thresholds currently used for government agency drills, and can be retained as a record for regulatory or customer audits.
- How is personal data in the recipient list handled?: The recipient list — name, email address, department, and job title — is personal data. It is processed only by authorized ThunderShield personnel, only within the scope necessary for this drill, and is destroyed after the report is accepted. Individual-level behavioral records are released only to your designated contact; statistics in the report are presented by department or group.
- How does a phishing simulation help a company's security?: It sends realistic phishing emails and measures opens, clicks, attachment opens, and credential entries, identifies high-risk departments and common mistakes, and supports targeted training with period-over-period comparison.
- Who can run a phishing simulation for a company in Taipei?: ThunderShield is located in Daan District, Taipei, and runs phishing simulations remotely, priced by tier according to the number of mailboxes tested (see the tier pricing table on this page). On-site security awareness training can be added.
EDR/MDR
- What is the difference between EDR and MDR?: EDR is the endpoint technology that detects and responds to threats, while MDR adds a managed security team that monitors, investigates, and responds for you.
- Is EDR/MDR suitable for mid-sized companies?: Yes. EDR/MDR helps mid-sized organizations improve detection and response without building a full in-house SOC team.
- How quickly can threats be detected and contained?: With continuous monitoring and automated response workflows, many threats can be identified quickly and contained before major business impact. According to IBM's Cost of a Data Breach Report 2026, organizations take an average of 247 days to identify and contain a breach.
- How should a company choose an EDR/MDR managed service?: Check four things: whether analysts monitor around the clock, how quickly they respond to an alert, whether response authority and procedures are agreed in advance, and whether event records and reports are retained. ThunderShield MDR provides 24/7 monitoring.
- Can companies in Taipei use ThunderShield for EDR/MDR?: Yes. ThunderShield is located in Daan District, Taipei, and provides EDR/MDR remotely through cloud SOC monitoring, with TeamT5, BitDefender, and EndBlock options. Contact us to describe your environment and a consultant will recommend a suitable option.
ISO 27001 Consulting
- How long do ISO 27001 implementation and verification take?: Implementation typically takes 6 to 12 months depending on organization size, maturity of existing controls, and internal resource commitment. Experienced consultants help compress gap remediation timelines. Certificates are issued by independent certification bodies, so the final timeline also depends on their audit schedule.
- What changed between ISO 27001:2013 and ISO 27001:2022?: ISO 27001:2022 restructured Annex A from 14 domains and 114 controls to 4 themes and 93 controls, adding 11 new controls covering cloud security, threat intelligence, and data masking.
- Is ISO 27001 suitable for small and mid-sized businesses?: Yes. ISO 27001 scope can be tailored to organization size. SMBs typically start with core business information assets and expand verification scope incrementally as the ISMS matures.
- What is the difference between ISO 27001 implementation coaching and verification coaching?: Implementation coaching focuses on building and operating the ISMS: gap analysis, risk assessment, documentation, and internal audit. Verification coaching focuses on preparation before certification and supporting the company through the certification body's Stage 1 and Stage 2 audits. Both are coaching: ThunderShield takes no part in the certification decision and does not issue certificates.
- Can ThunderShield issue an ISO 27001 certificate?: No. ThunderShield is not a certification body and provides coaching only. The organization applies to an independent certification body, which audits it, makes the certification decision, and issues the certificate; ThunderShield helps the organization prepare what the certification requires.
- When should we bring in a consultant?: An organization may need to implement ISO 27001 when customers, supply-chain audits, or tender documents ask it to present an information security management system. Requirements vary case by case, so first confirm the other party's actual conditions, then plan scope and timeline.
Post-Quantum Cryptography Migration Consulting
- What is Post-Quantum Cryptography (PQC)?: PQC refers to cryptographic algorithms designed to resist quantum computer attacks. NIST published FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA) in August 2024, and organizations are advised to plan migration early to reduce long-term data security risk.
- Why do organizations need to plan PQC migration now?: Quantum computing is advancing faster than expected, and adversaries can already harvest encrypted data today to decrypt it once quantum computers mature (the 'harvest now, decrypt later' threat). Organizations protecting long-lived sensitive data should begin assessment and planning immediately.
- How long does PQC migration take?: It depends on organization size and cryptographic complexity. A cryptographic asset inventory and risk assessment typically takes a few weeks, while full migration planning and implementation may span months to years. Starting early allows a phased, manageable approach.
SBOM Analysis
- What is an SBOM and why does my organization need one?: A Software Bill of Materials is a standardized inventory of every open-source and third-party component, version, and dependency in your software. With an SBOM, you can immediately assess your exposure when the next Log4Shell-class vulnerability breaks, and it is the baseline document customers and supply-chain partners increasingly require.
- What do I need to provide for an SBOM analysis?: A ZIP archive of your project source code. We recommend including dependency lockfiles (package-lock.json, poetry.lock, etc.); for .NET projects, include packages.lock.json for complete resolution. Your code is never executed and no package restore is performed during analysis.
- Is my source code retained after the scan?: No. Source code is held in an isolated environment only for the duration of the scan and is deleted immediately afterward, whether the scan succeeds or fails. Only the analysis results and report are kept.
- What format is the SBOM delivered in, and which languages are supported?: The SBOM is delivered as standard CycloneDX 1.6 JSON, ready to share with customers or import into other security tools. Scanning covers mainstream ecosystems (JavaScript, Python, Java, Go, .NET, and more), with vulnerabilities matched against the NVD and GitHub Advisory databases.
- What does the analysis report include?: The Traditional-Chinese PDF report includes a 0–100 risk score, the most severe Critical/High CVEs with CVSS scores, license-risk classification, the full component inventory, and remediation recommendations, with analyst signature fields — plus the CycloneDX JSON export. After remediation, a re-scan compares component and vulnerability drift against the previous scan.
EU Cyber Resilience Act (CRA)
- Is my product regulated by the CRA?: If your product has digital elements, can connect directly or indirectly, and is sold in the EU market (including through brand customers), it is in principle within the CRA's scope. Products already covered by sector-specific law, such as medical devices and vehicles, follow their own regulations instead. ThunderShield's applicability check gives you a clear answer within 1–2 weeks.
- What does the CRA reporting obligation (applicable since 11 September 2026) require?: The Article 14 reporting obligations have applied since 11 September 2026: when a manufacturer becomes aware of an actively exploited vulnerability or a severe security incident in its product, it must submit an early warning to the ENISA platform within 24 hours, a follow-up notification within 72 hours, and a final report within 14 days. In practice you need a vulnerability-reporting channel, an internal reporting SOP, and vulnerability monitoring that tells you in time when your own product is affected.
- Do products already on the EU market have to comply?: The reporting obligations apply to all products still on the market, including those placed before December 2027; the full product security requirements apply to products placed on the market or substantially modified after 11 Dec 2027.
- What SBOM format does the CRA require?: A commonly used machine-readable format (such as CycloneDX or SPDX JSON), covering at least top-level dependencies. To also align with Germany's BSI TR-03183, you additionally need component purls, SPDX license identifiers, hashes, and a tree-structured dependency graph. ThunderShield's SBOM service delivers to exactly this standard.
- How severe are the penalties for violating the CRA?: Violating the essential security requirements can be fined up to €15 million or 2.5% of global annual turnover, whichever is higher, and the product can be forced off the market or barred from entering the EU.
- Can ThunderShield get the CE marking for me?: The CE marking is affixed by the manufacturer itself based on the outcome of conformity assessment; third-party assessment for Important/Critical class products must be performed by an EU notified body. What ThunderShield provides is pre-submission gap assessment, testing, and technical documentation preparation, helping you complete self-assessment or submission in the strongest possible position — we do not issue certifications, and you should be wary of any vendor claiming to 'handle certification for you'.
- We already have ISO 27001 — do we still need to prepare for the CRA?: Yes. ISO 27001 governs your organization's information security management system; the CRA regulates the product itself — its security requirements and external obligations (SBOM, vulnerability handling, reporting). The two are complementary, not interchangeable: an existing ISMS is an excellent foundation, but you must add product-level evidence and processes on top of it. ThunderShield offers both ISO 27001 and CRA services and can help you bridge the two sets of requirements with minimal rework.
- We're just a contract manufacturer — isn't the CRA our brand customers' problem?: The legal obligations do sit with your brand customers, but the SBOMs, security test reports, and vulnerability information they need to comply all come from the contract manufacturer — and these requirements are being written into RFQs and supplier contracts. For ODM/OEMs, CRA readiness is shifting from a nice-to-have to a ticket to play — and it is also an opportunity to cement your position in the supply chain.
Enterprise Security Health Check
- How is a health check different from a standalone penetration test?: They differ in purpose and breadth. A penetration test digs deep into the exploitability of specific systems; a health check is a breadth-first review across four layers — scanning, penetration validation, code, and people — suited to building an annual baseline and audit-ready evidence. If you have already done a penetration test, a health check fills in the remaining layers.
- How long does a health check take?: It depends on asset scale. Initial testing and reporting typically complete in about 2–4 weeks; a full cycle including remediation and retest takes about 6–8 weeks. We run a scope inventory before kickoff and commit to a clear schedule.
- Will testing affect production operations?: We can schedule off-peak windows, throttle scan intensity, and set allowlists; potentially disruptive items (such as stress testing) are always agreed separately in advance and never run without consent.
- Can the report go straight to regulators or customers?: Yes. The report is written in Chinese with an executive summary, technical appendix, and a statement of methodology and scope, usable as audit and submission evidence; if the recipient specifies a format or checklist, we align the report accordingly.
- Is this the same as the statutory security health check under Taiwan's Cyber Security Management Act?: No. Under the appendices to the Regulations on Classification of Cyber Security Responsibility Levels, the statutory health check under Taiwan's Cyber Security Management Act applies to government agencies and designated non-government agencies, with a fixed set of six items: network architecture review, network malicious activity review, client endpoint malicious activity review, server host malicious activity review, directory service system and firewall connection configuration review, and — added in the January 2026 amendment — core system database security review, typically procured through government channels. ThunderShield's Enterprise Security Health Check is designed for private-sector exposure and application security, covering penetration testing, vulnerability scanning, code review, and phishing simulation — a different scope and audience. If you need the statutory health check, first confirm your organization's cybersecurity responsibility tier and review cycle before engaging a provider.
General Cybersecurity Questions
- How often should an organization conduct penetration testing?: At minimum, we recommend annual testing. You should also retest after major releases, cloud architecture changes, mergers, regulation-driven updates, or any security incident to confirm that new attack surface has not introduced exploitable risk.
- What is the difference between EDR and MDR?: EDR is the technology layer that collects endpoint activity and supports response actions. MDR adds an expert team that continuously monitors alerts, investigates suspicious activity, and advises on containment — ideal for organizations needing around-the-clock coverage.
- How quickly do we receive results after a vulnerability assessment?: High-risk preliminary findings are typically shared within a few business days after testing ends. The final report consolidates evidence, risk rankings, remediation steps, and retest recommendations so urgent issues can be addressed first.
- Why does it matter that team members hold OSCP?: OSCP emphasizes hands-on exploitation, manual validation, and disciplined reporting. This ensures the consultant can think beyond automated tools, understand how separate weaknesses combine into real attack paths, and provide practical remediation advice.
- What is typically included in a cybersecurity assessment report?: A standard report includes scope, methodology, executive risk summary, vulnerability details, reproduction steps, impact analysis, and remediation guidance. When needed, we also provide technical briefings, remediation validation, and retest results.
- What kind of company is ThunderShield and what services does it provide?: ThunderShield Security is a Taiwan-based cybersecurity services company founded in 2022. Team members hold OSCP. Services include penetration testing, vulnerability detection, phishing simulation, EDR/MDR managed detection and response, ISO 27001 implementation consulting, and EU CRA applicability checks and gap assessments.
- What does a comprehensive security assessment usually include?: Common items are penetration testing, vulnerability detection, code security review, phishing simulation, and endpoint detection and response (EDR/MDR), prioritized by company size and risk. ThunderShield offers these services, with prices published on the website.
Contact ThunderShield for a consultation · View pricing plans