Welcome to the Center for New American Security's National Security Startups podcast series, hosted by Senior Fellow and Director of the Technology and National Security Program, Ben Fitzgerald. Welcome, everyone, to the latest in our National Security Startups podcast series. We're joined today by Nealu Razie-Hau, who is currently the Chief Strategy Officer at RSA, a major information security company. Nealu, welcome.
Thank you. It's great to be here. So, by way of background, Nealu has a really diverse and amazing set of experiences across her career. She's been a management consultant at McKinsey.
She's working venture capital at Paladin. She's been a Chief Strategy Officer for a venture-backed startup at Endgame, and is now running strategy at a major commercial information security technology company. Nealu, it's a great opportunity for us to cover a pretty wide range of things. I just wonder if you could start out by telling us a little bit about RSA and what you do there.
RSA is a pretty interesting company, and the information security space, we're different than most. First of all, we've been around for 30 years, and we have a real history of innovating in some pretty important markets, everything from commercial cryptography to two-factor authentication to network forensics. We kind of blaze the path in those areas, and we continue to do that. We're a big and profitable company.
We have 30,000 customers, including over 90% of the Fortune 100, pretty much 19 out of 20 in every major vertical. We have over 1,000 technology partners. Our suite of products covers everything from network monitoring, analytics, and forensic, to identity access and assurance, governance, risk and compliance, fraud, a great suite of anti-fraud products. And we also have one of the best incident response teams in the industry.
So that really helps us stand out from the 1,500 or so companies that are competing today in the cybersecurity space and gives us a pretty unique perch from which to participate in that market. So in terms of this conversation, I might start just by asking you to sort of hop back to a couple of years in the past. You've invested in startups. You've led startups.
You've acquired startups. You've competed against startups. When you think about that entire community, 1,500 competitors in the cybersecurity space, what do you think that that entire community can provide to the Department of Defense? Why should the DOD want to work with startups?
I'm glad you're starting with that. So I've been now in a big company for about 10 months. I spent over a quarter century working in the early-stage startup space. So this is a great question.
And really, the thing that startups can bring to government, to Defense Department, is innovation, innovation, innovation, right? Disruption, rapid response, and agility, especially in markets that have near-term commercial applicability, but where the government has a real need. When you look at the federal budgets today, most of it is spent on acquisitions in O&M. R&D, again, especially R&D in markets where the commercial companies are also feeling the pain, belongs to the private sector.
And from a mission perspective, it's really a win-win for DOD to find a way, for government in general, to find a way to partner with these companies, because 90% of our critical infrastructure is in the commercial sector. It's not owned by the government anymore. And so if we're going to fulfill our national security mission, we need to enable these companies that are coming up with the most advanced solutions for the issues that we're facing. So if you can partner effectively, we actually will do better in our national security mission.
So that's a very thoughtful and articulate way of framing the opportunity. There's a big if at the end of it, though, which is the challenge, which is if the government can engage properly. And as much as we talk about the need for innovation, and I think the government, the DOD, genuinely wants it. It's not necessarily comfortable doing the work required.
It doesn't like being disrupted. It wants the cool technology, but doesn't want to do the work. So from your perspective, whether that's from a VC or running a startup or a major technology company, what are the big challenges or obstacles that you see in working with DOD or getting those incentives aligned effectively? Yeah, and you're absolutely right about this.
I mean, we have a Secretary of Defense who is very committed to bringing technology in. We've had it in the past. Various folks inside DOD and the government broadly are committed to bringing it, and yet we're still not making it work. And the fundamental issue is aircraft carrier procurement process and timelines don't work in the technology industry, and we simply haven't found a way to adjust how we do procurement, how we interact with companies, how we share information between an early-stage company started by youngest kids who maybe have no background in government.
So the long sales cycles with the government require huge investment, and that's really hard for a young company that should be bootstrapped. Customization. The government needs a solution that works for its systems, and its systems are often very, very different and sometimes outdated relative to what's going on in the commercial market. And that customization can really lead startups astray.
Classification and clearance is also a significant problem. In the startup space, you don't tend to have founding teams who have the clearances you need to have the conversations to really understand what the operational requirements are. And so the conversation is blocked both ways. On the one hand, the startups don't know what the needs are.
On the other hand, the government agencies don't understand the art of the possible. And so a lot of that is in the realm of business infrastructure and compliance and all that management that startups tend not to have. Now that you're part of a large business, how do you think about those similar challenges and the DOD government marketplace? Is it similar dynamics?
How is it the same? How is it different? So the dynamics are pretty much the same. I mean, the positive side, by the way, of having the government as a customer is that it can be an immense windfall, right?
If you can get into a program, you can have large contracts, you can have visibility into the revenues in the future. And that means a lot, whether it's a small business or a big business. But whether you're at a large company or you're at a small company, it's the same set of questions, right? Every decision you make, it's a trade-off in terms of ROI.
If I put my time, my energy, my dollars against the government vertical, will I get the same return as I would if I put it against financial services, if I put it against manufacturing, if I put it against retail? So you do face the same issues. Now, theoretically, the products are more mature in a large business. And certainly at RSA, we have a very robust business with the government.
A significant portion of our revenues come from the government space. We have a suite of products that works really well in meeting government requirements. But even for us, as we think about investing our resources, there's a massive commercial opportunity. 70-some-odd billion dollars are being spent in information security, and that number is only growing.
The procurement cycles are very fast. The other thing for us that really matters, one of the things that makes RSA difference, as I mentioned, is that we continue to innovate. And so I recently met with a CISO of one of the major financial institutions. They're not only a large customer, but every time we come out with a new product or a new feature because we're a trusted partner, they raise their hands and say, hey, let us be your data partner.
Let us help you define the roadmap. Let us test this in our systems, and we'll give you feedback. That conversation doesn't happen as easily with the government customer. So, you know, big businesses, small businesses, we face the same kinds of challenges.
We might have more resources and more ability to understand what the process looks like. Certainly at RSA, we have a lot of clear people. We have folks who come out of government, out of DOD, out of the intelligence community. So we know what those procurement processes are.
But we have the same challenge everyone else does. And so just following up on this idea about ROI, if you are a large, diversified business like RSA, you have a much larger market that you can prosecute in the commercial space, and you're probably going to get high return on investment in a shorter time frame, which makes the question, why would you continue to focus on DOD? And do you have to make trade-offs where it's like, well, we would like to do more work with the department, but we can't afford to apply resources to that when we could go after a different market? Well, so again, it comes back to the plus side of doing well with government agencies and the Department of Defense is that, you know, you have visibility into repeatable revenues over time.
So if you can crack the code, then you can have a great business working with the government. You need to bring them solutions that work. And again, we have a pretty mature stable of products, so it's pretty easy for us to bring our products into the government. The mission matters, too.
I mean, for a lot of us at RSA, the mission truly matters. We want the government to succeed. It's really important for the government to succeed. Both commercial and government have to succeed for us to fulfill the national security mission.
So we do invest in going after that market. But as I said, it's kind of a zero-sum game at the end of the day, and you've got to make the right trade-offs and really think it through. And so just changing gears a little bit and thinking again about this challenge of ROI, one of the things that we see is that from an investor's perspective, that you could expect a much larger multiple or return on that investment for a company that's prosecuting a larger market rather than focusing purely on the Department of Defense. So when you were making investment decisions, did you value pure defense-focused businesses differently to commercial?
And did that make you more or less willing to do that? I'm just interested in your investment theory and expectations. So there is absolutely a difference between how you value a company that's exclusively focused on providing solutions to the Defense Department versus a company that's going after a large commercial market opportunity. It's an order of magnitude difference in terms of the multiples that any investor or acquirer would apply, the difference between 0.5 to 1x revenues to 6 to 100x revenues, depending on the type of market you're going after.
But it doesn't mean that you write off companies that are starting in the federal government. So the place that becomes really interesting is where there's a very large commercial opportunity, but the government is an early adopter. And companies that are going after that, you would treat differently. Now, you need to make sure that that company is set up for success because they can go down 1,000 raffles trying to serve the government customer, the customization, as I said.
They can be led astray from the big commercial market opportunity. But if they're disciplined in terms of understanding what the big market opportunity is as they service the government customer, if they have the people in the support network, whether it's investor-based or folks inside the company who come from government and understand how to have those conversations, have the right clearances, know how to understand and interpret the operational needs, then you don't discount it. So that's really sort of the difference between a commercially-focused company that is serving a government need versus an exclusively government-focused company. Because at the end of the day, that market just isn't that big, and for a small company to take on the big systems integrators, there are very, very, very, very few who've won that battle.
Yeah, exactly. And it's fascinating to your point about customization. It's not just product customization. It's your business model customization.
You'd very easily end up optimizing your accounting systems and all that stuff to work for a government client and have a business which really is not structured to work for a commercial or a commercial marketplace. Absolutely. I mean, the commercial market is incredibly dynamic. You have to be agile.
You have to be able to adapt it as an exchange, especially in markets like the cybersecurity market. And so culturally, if you go down that sort of government service, it's really hard to tack toward the commercial market. Yeah, and so the challenge for me as I think about that is I completely agree with you, and I think the theoretical opportunity is clear. And we've seen a few instances now with startups that have done it.
Endgame is an example. Palantir, I think, is probably the case in point. SpaceX is doing interesting stuff, and certainly companies like Dataminer are able to play both sides with that. But we're also starting to see defense contractors go after some of those commercial or previously commercial opportunities.
So I think specifically during the cyber area, we've seen Raytheon doing some interesting mergers and acquisitions recently. Lockheed Martin has been making a play for commercial business. Do you see that trend continuing, and are they competing for the same opportunities, or are they just looking the same from the outside? And how do you think that's going to play out?
So with respect to the systems integrators, they're facing a very harsh reality in terms of their core business with the government. It's shrinking. They don't have a choice. It's unlikely that they're going to be the lead innovators in these markets, but they certainly can make acquisitions in the market.
Historically, they haven't been great acquirers, so when they've acquired sort of fast tech companies, I don't know too many cases where it's actually ended up working out positively for them. I think as they refocus now and realize that they've got to succeed in the commercial markets, hopefully they'll adapt how they do business to be able to do that. On the flip side of it, a company like Endgame is a great example of really serving the government customer, but against a very broad commercial market opportunity and a need that's faced acutely in that market. So it's a good example of how you can be successful as a startup and expand into the commercial market the way you need to in order to be successful.
Palantir is an interesting example because they were born at a time when a lot of money was being spent by the DoD. We were losing two wars simultaneously. They were desperate for solutions in the field that really worked and gave us the advantage that we needed. So they came into being at a time when there was an acute need and a lot of money going after it, and they managed to go for that opportunity really well.
I think we need to – there's a lot of areas – space is another example. There's some really good examples of areas, again, where the government has a need. Cyber is a really good one. But that same need is felt in the commercial market.
And hopefully everyone will start to work better together, the startups, the systems integrators, and the government. That becomes the win-win-win scenario. So I'm going to ask you a slightly dangerous hypothetical question here. You've run strategy for two businesses recently, and you've provided professional advice to many.
If you were running strategy at a major defense company, how would you capitalize on the opportunities associated with startups? Do you do you think you're interested in them? We've seen some tension that defense specialists feel that can be innovative, which I think there's some truth to that. But if you were in one of those big organizations, how would you help them capitalize on these opportunities?
So theoretically, defense contractors can play a really interesting role in this process, right? They have the reach. They have the relationships. They have the contracts.
They have the clearances. They can actually become the clearinghouse for innovation to get products very quickly into the government and really get – they've already broken through all the structural conflict that early-stage companies face. So if you could, as an LSI, bring the different parties together and use that collaborative power you have in terms of understanding commercial, understanding government, having huge reach, and really create greater visibility amongst the players and a way, an avenue to get these disruptive products into the government, I think that would be phenomenal. You have to figure out how to make it work economically for everybody.
But that's really the power that those system integrators can bring until we fundamentally solve the bigger problem, which is how you fix the procurement process fundamentally from the ground up, right? Yeah, absolutely. So it's fascinating. The challenge right now is that as a function of the procurement system, the DOD is not necessarily creating opportunities for those lead systems integrators, the LSI's, to do that.
So they could bring these companies through, but then you have this issue of is there a requirement for what they're doing? How are they going to bring it in? The other challenge is, as someone who ran a small business, wanting to work with some of those guys, the current model is DOD would lay a requirement, the lead systems integrator would win the business, and then they would flow it down through their network of subcontractors. It was a sort of paternalistic kind of system, which is a little bit different when you're talking about bottom-up innovation.
So figuring out that dynamic is going to be challenging. And I think we're seeing instances of some of those big systems integrators looking to do that. The question is the economics and the model, how do we make that work? Absolutely.
Do you have a solution? So the challenge that we see with all this stuff, though, is it comes back to how the DOD can make itself more appealing. And in this context, obviously, we're thinking about this for startups. It's true for all sorts of businesses.
But I'd be interested in your thoughts on how the DOD can make itself more appealing across the board. You've already talked about some important things in terms of leading-edge problems, that kind of stuff. I'd just be interested in your thoughts on how we can create an environment where we can capitalize on those natural advantages. So this fundamentally feels like a Groundhog Day question to me.
I mean, since I've been in Washington working with technology companies and with government agencies, we've been asking this question. And somehow, regardless of the commitment from the top, and again, we have a commitment from Ash Carter, from Secretary of Defense Ash Carter, we can't seem to solve it. So, I mean, the answers are simple, but the implementation, the execution of them is incredibly complicated, right? You have to create a better process for sponsoring companies for clearances so that the conversations can happen.
You have to create a more agile acquisition process because we are, in the private sector, we're innovating. use agile software development. I mean, you know, versions happen every few weeks sometimes, which is just something the government doesn't know how to deal with. We've got to solve the language barrier between the two communities.
And by the way, it brings us to a real talent issue we have. I think we've got to, and there are certain agencies where NDHS is doing this, that are creating a process for people to be able to go back and forth between government and private sector. I think that becomes critical because that's how you solve the language barrier, that's how you solve the cultural barrier, that's how you create better understanding for each other's processes and each other's priorities. So if you had a way for government, you know, talent people in government to leave, go work in the commercial sector for some period of time, and then come back without any penalty, and vice versa, have a way for bringing commercial people into government, and then they can go back to their day jobs, I think you can start solving the problem, creating that deep level of understanding between the two communities so that we're not wary of each other, but actually understand what makes each of us tick and why we have to operate the way we do, you know, why transparency matters so much in government acquisition process, why return on investment matters so much, you know, for a business, that becomes, that could be a pathway to doing that.
It makes so much sense, even from the perspective of allowing people to be able to afford to do what they want to do. I think about this frequently in sort of the context of this third offset strategy that we're talking about with future technologies being all about artificial intelligence and machine learning, and the DOD wants to get into this space. If you think about what someone coming out of grad school can earn, and the general metric is, it's about the same ballpark as a first round NFL draft pick, and then you think about what senior executives in the Pentagon make, which is maybe a third of that, if you're lucky. How can we hope to compete effectively unless we let people have access to those income opportunities?
At the same time, would you rather be working on machine learning, which figures out how to get someone to click on something for buying true laces on the internet, or would you like to do machine learning for how to help someone running an HADR mission? It becomes very different. That's absolutely right, and I think there's opportunities, well I know, there's opportunities in the government that doesn't exist in the commercial sector, right? We don't have title authority in the commercial sector, so being able to work in cyber with an agency that has title authority to do things that are illegal is pretty damn cool.
Exactly. Taking those lessons to help protect infrastructure is really important. So there's a way to do this. I have faith.
And just for some of our listeners who don't live in the arcane walls of title authority, could you just unpack what you mean by that? Well, so the Department of Defense and the intelligence community are allowed to do offensive operations, and the commercial sector is not. And the ability to do that lets you, you know, gives you visibility into how adversaries behave. So if your job is to protect critical infrastructure against adversaries rather than, you know, setting papers, what better thing than to have participated in that mission at some point in your career?
That's right, and so if you've been able to do that, you would actually be, you would have the opportunity to take a more senior position or a more highly paid position. It makes a lot of sense, and if we can get those people back, that would be great. So following up on this point about different perceptions of folks, you've been able to look at this problem from multiple vantage points. How do you think the different groups, the different actors perceive each other or misperceive or misunderstand each other, whether that's DOD to startups or defense industry to technology companies?
What are the dynamics there? So in general, I do think that there's a relatively good understanding between both parties, and both sides have very good intentions, right? And I think sort of at a very high level, everyone gets it. We know what the government mission is, and we know, generally speaking, that to succeed in the commercial world, we have to be profitable at some point in your career.
But the biggest issue is that there isn't finger field between the two communities in terms of what that actually means, right? So what does it really mean to be a DOD in the acquisition process, in the procurement process? How do you deploy technologies? What's the reality of these massive systems that are incredibly complicated?
What does it feel like to own a P&L and to be accountable to a board that can fire you if you don't meet your numbers? And that's, again, goes back to that talent conversation. If we could find a way to have more exchange between the two groups and have a better finger field of exactly what this means for each side, not just theoretical understanding, I think that can help solve it. But I think at a high level, people get what government's supposed to do, people get what the role that private industry is supposed to serve.
We need to get that finger field. Yeah. And I mean, there's a common theme throughout this entire podcast series and this conversation more broadly that everyone kind of knows what we need to do. This is how do we actually execute and how do we do that in a way that will be successful?
We've been talking about this for decades and not a lot has necessarily changed, which makes me both optimistic and pessimistic at the same time. So I'm not sure what to do with that. So the last question that I would like to ask you, Nilo, is just about advice. You have a fantastic range of experience and I would like to offer up some free advice to our listeners who would otherwise not be able to get access to this.
What advice do you have for folks who are running or thinking about founding startups that are in the national security space or have a national security focus? What are those first few steps that can set you on the right path instead of hedging you in when you shouldn't be? So first I would say really think long and hard about why you're doing it and make sure that it doesn't take you off of your core business, which I would hope is solving a very large commercial market problem. You need to surround yourself with people who understand how the government works, how the government procurement process works, how you get into programs, which is really how you sort of get that long-term visibility into revenues.
There are investors who understand that incredibly well on both coasts, by the way. And it's not just about the valley. There are amazing investors on the east coast who are very, very good at helping companies. And these are typical venture funds I'm not just talking about in Qtel.
But there's a lot of funds where they have a good history and good relationships back into government. Having said that, it's really tough. There are very few companies that have been able to start their business focusing on the government customer and have managed to succeed over time. The commercial market is just a significantly larger market.
Don't take your eye off the ball with respect to that. And I do think solving this becomes really, really important. And I have faith that if we are aligned and committed to it, we can do it. Winston Churchill has this awesome quote, success is the ability to go from one failure to the next with no loss of enthusiasm.
We can get to success no matter how many times we fail at this. And getting to success is really important. We're not there yet. So for any startup that's really focusing on selling into DoD, you've got to be really careful and you've got to be really wary and you've got to make sure you've got the right advisors.
But if you have a solution that's going to improve the national security mission, don't give up on it. It's really important. I agree. And I was going to ask you another question, but I don't think that we'll have a more uplifting end note than this is an important thing to do, which I completely agree with.
So on that note, thank you so much for taking the time to be with you and good luck with making RSI a huge success. It's great to be here. To hear more from the National Security Startup Series, go to startups.cnas.org or search for CNAS on iTunes or SoundCloud.