Subject · 1 guide

Security

Pentesting · cyber compliance · fraud and AML

Security guides are written for the people who have to answer a customer security questionnaire, prepare for an audit or stop fraud without blocking good customers. In B2B software, security is part of the sale: buyers ask for test reports, compliance attestations and policies before they sign, and a weak answer can stall a deal for weeks.

We cover penetration testing, compliance frameworks such as SOC 2, ISO 27001 and PCI DSS, and fraud and anti-money-laundering controls. For each one we quote what the framework or regulator actually requires, which is often less specific than vendors suggest, and we explain what auditors and customers usually look for in practice. Where a requirement is only proposed, or the official text is behind a paywall, we say so.

Our guides also compare delivery models and costs. A traditional consultancy test, a penetration-testing-as-a-service platform, a bug bounty and an automated scanner answer different questions, and buying the wrong one wastes money and still leaves the questionnaire unanswered. We publish price ranges where reputable sources do and explain how scope drives cost. We also explain how to read a test report, what a retest should confirm and how to present results to a customer's security team.

Each guide ends with a verdict on what to buy, when and how often. These guides explain and compare; they are not a substitute for a qualified assessor, auditor or lawyer. Start with the penetration testing guide, and read the AI agents guide if you are adding AI systems that touch customer data.

  1. Thesis 005 · Security

    The complete guide to penetration testing for SaaS companies

    How SaaS companies should buy penetration tests: what SOC 2, ISO 27001, PCI DSS and HIPAA expect, test types, delivery models, costs, scoping and retests.

    Oct 23, 2026 · 19 min read