Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise RFPs Now Require Vendor Penetration Testing
Transcript
- Lucas: So Luna, I was reading through a recent enterprise RFP for a logistics platform, and I noticed something interesting. In the security section, they didn't just ask for a SOC 2 report or a filled-out security questionnaire. They explicitly required 'a third-party penetration test conducted within the last twelve months, with the full executive summary attached.' Not just attestation, not just a checkbox. Luna: That's a big shift. A few years ago, most buyers were satisfied with a completed questionnaire and maybe a copy of your SOC 2. Now they want the actual pentest report? Lucas: Exactly. And this isn't an outlier. More and more RFPs, especially in regulated industries like finance, healthcare, and even manufacturing, are making penetration testing a mandatory requirement. They want to see that you've had independent hackers try to break into your product, and they want to see what they found. Luna: Where does that come from? Is it just because of the high-profile breaches we've seen, or is something else driving it? Lucas: Part of it is a response to a specific incident, actually. In 2023, a major logistics provider suffered a breach that originated from a vulnerability in a third-party vendor's software. Since then, procurement teams in that sector have really tightened up. But it's also a broader trend. Regulators are pushing for more rigorous vendor risk management, and buyers are realizing that a SOC 2 report is essentially a point-in-time audit. It doesn't really tell you how secure a product is today. Luna: So the pentest is kind of a more current, more actionable snapshot. Lucas: Right. And it's not just about the existence of the test. Buyers are now asking for specifics: when was it conducted, who did it, what was the scope, and critically, what were the findings and how did you remediate them. We're seeing RFPs that ask for the actual executive summary, which is a pretty significant change in transparency. Luna: I can see why vendors might be hesitant to share that. It's like showing your work, and you're worried about revealing weaknesses. Lucas: Yeah, and that's a real tension. But the best vendors are starting to embrace it. They see it as a way to differentiate themselves. If you have a clean pentest report from a reputable firm, it's a strong signal that your product is built with security in mind. And if you have a few medium-severity findings that you've already remediated, that's actually a healthy sign. It shows you're testing regularly and fixing issues. Luna: So it's not just about having zero findings, it's about how you handle the findings. Lucas: Exactly. And this is where the conversation gets practical. Let's talk about what a pentest actually is, because there's a lot of confusion between a vulnerability scan and a real penetration test. A vulnerability scan is automated, it looks for known vulnerabilities, it's relatively cheap. A penetration test is a manual, human-led effort where security experts try to exploit vulnerabilities, chain them together, and simulate what a real attacker would do. It's far more thorough, but it's also significantly more expensive. Luna: And I'm guessing a lot of RFPs are demanding the latter. Lucas: They are. And that's creating a challenge for smaller SaaS vendors who might not have the budget or the in-house expertise to conduct a full pentest every year. The cost can range from twenty thousand to a hundred thousand dollars, sometimes even more for complex environments. And if a buyer requires it annually, that's a significant recurring expense. Luna: So what should a small vendor do? Are there ways to approach this without breaking the bank? Lucas: There are a few strategies. First, you can start with a well-scoped penetration test. Don't test your entire product suite if you don't have to. Focus on the core applications and the most critical data flows. That can reduce costs substantially. Second, look for vendors that offer pentest as a service with subscription models. Some firms now offer continuous penetration testing, where you get a smaller test every quarter, rather than a massive one once a year. It's more affordable and actually provides better ongoing coverage. Luna: And it shows you're not just doing a point-in-time test, you're actually committed to continuous security monitoring. Lucas: Exactly. And that's a story you can tell in your RFP response. But here's the thing: the buyer ultimately wants to see a report from an independent, reputable firm. So you can't just rely on internal testing. You need to invest in an external assessment, but you can be smart about how you scope it. Luna: What about the findings? I imagine the RFP might ask you to detail them. How should a vendor present that in a response? Lucas: That's a critical question. Let's say you have a penetration test summary that lists a few high-severity findings. The worst thing you can do is hide them or downplay them. Buyers will often ask follow-up questions, and if they discover you were evasive, that's a huge red flag. Instead, you should present the findings honestly, explain what you've already done to remediate them, and provide evidence, like a remediation plan and a timeline. That actually builds trust. Luna: So it's almost like the pentest becomes a conversation starter, not just a box to check. Lucas: Right. And some vendors go even further. They include the pentest methodology and scope details in their security whitepapers. That shows a level of transparency that really resonates with enterprise buyers. Luna: And are there any common mistakes you see vendors making when they respond to these pentest-related questions? Lucas: Yeah, one is treating the pentest requirement as a one-time thing. You might pass this RFP, but buyers are increasingly asking for proof of ongoing testing, like a 'continuous pentest' or a 'pen test on demand.' If you only have a single annual report, you might look behind the curve. Another mistake is not properly documenting the scope of the test. Buyers want to know exactly what was tested, what wasn't, and why. If your report says 'tested the external network' but your product is a SaaS application, that raises questions. Luna: Let's get into the practical side. If a vendor is new to this, how should they approach their first pentest requirement in an RFP? What should they do day one? Lucas: Day one is to understand the exact requirement. Read the RFP language carefully. Does it ask for a 'penetration test' or a 'vulnerability assessment'? Sometimes buyers use the terms interchangeably, but they're very different. If it's a full pentest, you need to budget accordingly and plan for the time it takes to conduct it, usually three to six weeks. If it says 'vulnerability scan,' you might be able to use a cheaper automated tool, but be careful, some buyers will specifically reject that. Luna: And what about the question of who conducts the test? Can it be an internal team, or does it have to be an external firm? Lucas: Most enterprise buyers require an independent third-party firm. They don't trust internal teams, no matter how skilled, because they might have blind spots or conflicts of interest. So you need to engage a recognized firm like a Big Four or a specialized security consultancy. The name recognition matters too. A report from a well-known firm carries more weight than an obscure one. Luna: But that can be expensive. Is there any way to negotiate or work around that? Lucas: You can sometimes negotiate the scope or the frequency. For example, if the RFP requires an annual test, you might propose a bi-annual test plus a continuous vulnerability scan, and make a case that it provides better coverage. Some buyers are open to that if you can demonstrate the logic. But ultimately, if the buyer is strict, you have to meet the requirement. So it becomes a question of whether the deal is worth the investment. Luna: That's a big decision for a small vendor. Are we seeing any trends in how buyers are enforcing this? Is it becoming a deal-breaker? Lucas: Increasingly, yes. A few months ago, I heard from a mid-sized SaaS company that lost a seven-figure deal because they couldn't provide a recent pentest report. They had one from two years ago, but the buyer required one within the last twelve months. That's a tough lesson. So it's not just a nice to have anymore; it's a competitive differentiator. Luna: And that's where the RFP language is getting sharper. We're seeing things like 'must have completed a third-party penetration test within the last nine months' or even 'within the last six months.' Lucas: Exactly. And some buyers are asking for the raw findings, not just the executive summary. That's a bit controversial, but it's happening. They want to assess the severity of the vulnerabilities themselves, rather than trusting the vendor's interpretation. Luna: How should a vendor handle that request? It feels like giving away your IP. Lucas: It's a delicate balance. You can argue that the pentest report is confidential and contains sensitive security information. You can offer to share it under an NDA, or you can summarize the findings in a way that addresses the buyer's concerns without exposing everything. But some buyers are stubborn and will walk away if they don't get the full report. It really depends on the leverage each side has. Luna: And then there's the question of what happens after you've provided the report. Do buyers actually review it, or is it just a box-check? Lucas: That's a great question. In my experience, the best buyers do review it. They have their own security teams who will scrutinize the findings and ask follow-up questions. They might even ask for a call with your security lead to discuss remediation. But there are also buyers who just want to see that a test was done, and they don't dig deeper. That's a missed opportunity for both sides. Luna: So it's not just about passing the checkbox, it's about having a real security program that you can talk about. Lucas: Exactly. And that's the mindset that helps vendors win. Instead of seeing the pentest requirement as an obstacle, see it as a chance to showcase your security maturity. A well-run pentest, with a clear report and a solid remediation plan, can actually be a selling point. Luna: Let's zoom out a bit. Where do you see this trend heading over the next year or two? Lucas: I think we're going to see more automation in the pentest space, with things like automated security testing integrated into CI/CD pipelines. That will make it easier for vendors to have continuous visibility. But the human-led pentest isn't going away, especially for high-risk environments. I also think we'll see more standardized frameworks for what constitutes an acceptable pentest report, so buyers can compare vendors more easily. Luna: And what about the vendors who are just starting out? Any advice for them? Lucas: Start early. Don't wait for an RFP to demand a pentest. Invest in a pentest once you have a product that's ready for enterprise customers, even if it's just a small scoped test. That way, you have a report to present when the opportunity arises. Also, consider using cheaper alternatives like bug bounty programs to supplement your pentest findings. They're not a replacement, but they can show a proactive approach. Luna: That's a smart way to build up a security narrative without breaking the bank. Lucas: Exactly. And one more thing, when you do get that pentest report, treat it as a living document. Update it regularly, and be transparent about your security posture. Buyers appreciate honesty, and it sets you apart from vendors who try to hide their weaknesses. Luna: So the takeaway is that pentest requirements are becoming a standard part of enterprise RFPs, and vendors need to adapt or risk losing deals. Lucas: Absolutely. And the vendors who embrace it, who use it as a chance to demonstrate their security commitment, are the ones who'll win. It's not just about checking a box anymore; it's about showing that security is part of your DNA. Luna: Well said. That's a great place to wrap up. Thanks for the insights, Lucas. Lucas: Thanks, Luna. And to our listeners, if you're a vendor facing these pentest requirements, don't panic. Take it one step at a time, and use it as an opportunity to strengthen your security posture.