Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Vendor RFPs Now Demand Board-Level Security Oversight
Transcript
- Lucas: So Luna, I was reading through a draft RFP from a Fortune 500 manufacturer this week, and buried on page forty-seven, they ask for evidence that the vendor's board of directors has reviewed and approved the company's cybersecurity strategy. Luna: That's a big leap from the usual 'do you have a SOC 2 report' question. Lucas: It is. And it's not just one company. I'm seeing this more and more in enterprise evaluations—a clause that essentially demands board-level accountability for security posture. It's not enough that your CISO says you're secure; procurement wants to know the people who set the risk appetite are paying attention. Luna: Interesting. So what does that actually look like in practice? A board resolution? A signed statement? Lucas: Great question. The request usually asks for a few concrete artifacts. First, a description of the board's role in overseeing cybersecurity, including which committee holds that responsibility. Second, the frequency of board-level security briefings—quarterly, semi-annually, that kind of thing. And third, sometimes they want the qualifications of the directors who oversee this, like a board member with a tech or security background. Luna: So they're trying to verify that security isn't just delegated down to the IT department and forgotten about at the top. Lucas: Exactly. And this shift didn't happen in a vacuum. The SEC's cybersecurity disclosure rules that went into effect in late 2023 forced public companies to disclose material cyber incidents and describe their processes for assessing and managing cyber risk. That pushed boards to formalize their oversight. Luna: Right, and I remember a survey from last year showing that a majority of CISOs now report to the board at least quarterly, and many feel direct pressure from directors to improve resilience. Lucas: That's the survey I'm thinking of—sixty-eight percent of CISOs said their boards now ask tougher questions than they did three years ago. So what we're seeing in RFPs is basically procurement codifying that expectation into their vendor due diligence. Luna: But does it actually move the needle? Or is this just another box-ticking exercise? Lucas: I think it's genuinely dual-purpose. For a well-run company, it's a way to separate vendors who take security seriously from those who treat it as a marketing slide. But there's also a real risk that it becomes a check the box thing if the response is just a generic paragraph about the board's commitment to security. Luna: So what separates a meaningful response from a hollow one? Lucas: Specificity, for one. A vendor that names the board committee, shares the meeting cadence, and gives an example of a recent board-level security discussion—that carries weight. A vendor that says 'our board reviews security annually' with no detail? That's a red flag. Luna: You know, this reminds me of how financial institutions were early adopters of board-level risk committees after the 2008 crisis. Now it's becoming standard practice in cybersecurity. Lucas: Precisely. And the enterprise folks I talk to say they're looking for evidence that security risk is treated like financial risk—something the board owns, not just the CTO's side project. Luna: Before you go further, I want to say — if this kind of analysis is helping you navigate enterprise sales or procurement, it genuinely helps us keep these conversations ad-free. There's a buy me a coffee link, at buy me a coffee dot com slash fexingo, if you ever want to chip in. Lucas: Appreciate that. And it's a small ask, but it does keep the lights on. So, back to the board oversight question—what should a vendor actually do if they get this in an RFP? Luna: That's the practical angle. If you're a SaaS company and you don't have a board committee yet, what's the first step? Lucas: First, don't panic. Not every company has a dedicated cybersecurity committee, and that's okay. The response should acknowledge what you do have—even if it's the full board that reviews security on a quarterly basis. The key is to be transparent and specific about the governance structure you actually have. Luna: And if you're a smaller company without a formal board, say a founder-led startup? How do you handle that? Lucas: That's a tougher position. Some startups respond by pointing to their investor board or advisory board. Others bring in an outside security advisor who reports to the board. The smart ones document that the founder or CEO personally reviews security metrics on a monthly cadence, and they make that visible in the response. Luna: So it's about showing that someone at the top is genuinely accountable, not just that a policy exists. Lucas: Exactly. And this is where I think the best vendors turn a potential weakness into a differentiator. I heard about a mid-sized SaaS company, maybe four hundred employees, that saw this question coming and proactively formed a board cybersecurity committee with an external expert chair. They used that in every sales pitch, and it won them a couple of big deals. Luna: That's a smart move. It's not just about answering the question—it's about signaling that you're ahead of the curve. Lucas: Right. And that's why I think this trend is more than just a checkbox. It forces vendors to think about governance in a way that many haven't before. And that has real implications for how they manage risk day to day. Luna: But I wonder, does this actually correlate with better security outcomes? Is there any evidence that companies with board-level oversight have fewer breaches? Lucas: There's some research that suggests a correlation. A 2024 study from the National Association of Corporate Directors found that companies with a board-level cyber expert had significantly lower average breach costs. But correlation isn't causation, and the sample sizes are small. Luna: Still, it makes intuitive sense. If the board is asking tough questions, the CISO is going to have to dig deeper into their own defenses. Lucas: Absolutely. And that's the direction enterprise procurement is heading. I expect this clause to become as standard as the SOC 2 request within a couple of years. Luna: So for our listeners who are on the vendor side, what's the one thing they should do today to prepare? Lucas: I'd say, look at your own governance structure with fresh eyes. Write down who at the board level oversees cybersecurity, how often they meet, and what they actually review. If you can't answer that in two sentences, that's a problem. Luna: And if you're on the buyer side, what should you look for in the responses? Lucas: Look for substance over form. A good response will name names and give examples. A bad one will be vague and aspirational. Also, check whether the board composition includes anyone with a technology or security background—that's often a strong indicator. Luna: It's interesting how procurement is becoming the enforcement arm for corporate governance. Lucas: It is. And it's a natural evolution. As security becomes a board-level issue, the people buying software want to make sure the vendors they bring into their ecosystem are held to the same standard. Luna: So do you think this will actually reduce cyber risk across the industry, or is it just another layer of paperwork that delays deals? Lucas: I think it's genuinely reducing risk, but not because the paperwork itself stops attacks. It's because the process forces vendors to think about security at a higher level. And that usually leads to better decisions about investment and staffing. Luna: That's a fair point. It's the thinking that matters, not the document. Lucas: And that's the takeaway I'd leave our listeners with. Whether you're selling or buying, treat this as a chance to have a real conversation about governance, not just a form to fill out. Luna: Well said. And if this episode gave you something to think about, we'd love to hear your stories. But for now, thanks for being here.