Charlotte Guiney: We’re not just doing this, we’re building on it. We’re looking at what’s next. We’re looking at how can we better defend the organization, not just reactively defend it.” I’ve never been in a situation, and this is throughout my whole career, where senior leadership has said no to that.
AJ Nash: Hello, and welcome to another episode of Needlestack. I’m AJ Nash, your host. I’m joined, as always, by co-host Kacper Piwowar. I’ll turn it over to him for a second. Just a reminder my background is about 19 years in the US intelligence community, another 11 or so, in the private sector. I’m an intelligence professional focused primarily on intelligence-driven security solutions and helping people get there. Kacper, tell them a little bit about yourself and then we’ll jump in.
Kacper Piwowar: Hey everybody. Hello again, my name is Kacper. I’m a senior product marketing manager at Authentic8. I’ve been with the company for quite some time, and I’ve been in the cybersecurity space also for quite some time. Mainly a corporate background by nature. excited to get into things today. This should be interesting.
AJ Nash: Yeah, and it’s gonna be a fun one ’cause we have a cool guest today. The shiny face that people don’t know who she is yet if you’re watching, but you’re excited to see cause she’s smiling and happy, is Charlotte Guiney. Charlotte’s a cyber threat expert, who made career stops at State Street Bank, the Federal Reserve Bank of San Francisco, and Splunk before taking on her current role as cyber threat intelligence manager for Toyota Financial Services, where she’s responsible for ensuring intelligence-driven security across the enterprise. So you know that speaks to my heart. Charlotte’s also a graduate of Brandeis University, where she majored in international global studies while minoring in both East Asian studies and business. Kacper, what are we talking about today, man?
Kacper Piwowar: Yeah. So we are talking about holistic intelligence for proactive defense with Charlotte today, which I think is very pertinent and relevant to all of our listeners. So with that, let’s just get into it, and let’s start to hammer away at this topic while we have you, Charlotte.
Kacper Piwowar: First thing, I think we all kinda wanna know is what does the concept of holistic intelligence encompass, and how does it differ, from how most organizations actually build their threat intelligence programs?
Charlotte Guiney: Yeah. I think generally threat intelligence teams are already maturing more towards proactive threat intelligence in a way from that traditional kind of government stereotypical type of intelligence. But that’s still how a lot of those teams and capabilities are being built out, because that’s where the expertise is coming from. No shade there whatsoever. We can grow from that one hundred.
AJ Nash: Right. It’s been nice talking to you, Charlotte. Okay. Now go on.
Charlotte Guiney: Um, but, taking that next step and to really benefit the organization that you’re working for, we’re looking at incorporating that proactive threat hunting. So you’re taking your intelligence in, you’re not having to just toss it over the fence to a threat hunter or to a SOC team. You know the priorities, you know the threat intelligence, you know your defenses. You can go and search for that level. And yeah, if there’s an incident, work with your incident team to then work on it. But otherwise, that’s the first step. And then as you get more comfortable and more mature in understanding your organization and your environment and what your threat landscape is, you can do more purple teaming, so you get to work with your red teamers, your pen testers, not just the blue side, and grow through that.
Charlotte Guiney: And even then, as you’re able to start testing your defenses and you really understand what your priorities are as an organization, you start incorporating a deception capability. So you’re talking honey tokens, honeypots, depending on how high or low interaction legal lets you go. And then finally, you’re able to really see all that information.
Charlotte Guiney: You’re getting high-fidelity threat intelligence. You’re doing the work yourself, and you can start doing that end-to-end threat research. So you’re also going out there, finding your own sources, able to test your own sources, and then provide the highest defense with the highest priority based on what your organization needs to defend through the same people, right through the same team.
[00:03:58] Kacper Piwowar: So would it make sense if I was to break that down, Charlotte, for somebody like myself, you kind of have traditional threat intelligence, or TI, focuses a lot on what happened. And then you have holistic intelligence, which is what you’re talking about, which is what’s happening right now and how can I actually engage with it?
[00:04:15] Charlotte Guiney: With it 100%. And you always are gonna have to have a certain level of reactivity when it comes to threat intelligence. There’s always gonna be an aspect to that. Part of the holistic threat intelligence theory that I’m building towards is you have to incorporate some automation to allow for that type of proactive research.
[00:04:36] AJ Nash: Well, yeah, and it’s interesting. So I, I mean, obviously I spend a lot of time in the intel community. Some of it’s proactive, some of it… A lot of it is reactive, of course. You know, there’s certainly been efforts to go there. But I think, interestingly, the way you described, you know, sort of this embedding, this purple team comes to mind, right?
[00:04:50] AJ Nash: So, in, in the government space, a lot of times you have, you know, blue team is, is, you know, us, the good guys, and red team is the bad guys, however you want to look at it. And then the private sector in cybersecurity, if you have red team, it’s actually emulating the bad guys, right? So, and then purple is that integration. And we had some of that in the government. It was normally known as like intel operations. So you had intel as like your A2 or your J2 org, and then operations as your A3 or your J3. And then they had this, like intel was an A23, which was your intel ops organization, right? But it’s not nearly as big or prominent, and it still ultimately is subordinate to the intel leader, not the operations.
[00:05:20] AJ Nash: And it seems like what you’re talking about is really this, uh, more of a merging and a melding of intel and operations together in a tighter loop is what I would say, right? And I experienced some of that. Well, this was actually a learning experience for me when I moved from the government to the private sector.
[00:05:32] AJ Nash: My first gig in the private sector was with a bank. And, you know, in retrospect, I look and say, “Well, I thought I was pretty smart,” and I did okay on some things. But I do remember, you know,
[00:05:41] AJ Nash: we’re doing intel products and I’m being told, you know, “Don’t… You know, you need to tell people what to do with this.”
[00:05:45] AJ Nash: And I’m like, “No, I don’t. That’s not how it works.” Like, my job is to tell them everything I can find out about it. You know, in the intel world, I don’t tell the trigger pullers which door to kick in, and which weapon to use. Like, I tell them where the adversary’s gonna be and what their capabilities are and all these things. Maybe we did some action analysis, and made some minor recommendations, but you’re really careful ’cause trigger pullers don’t want to be told which weapons to use and which doors to go into. And then here it was very much the opposite. No, the people taking actions in the private sector, in cybersecurity, don’t know what to do with what you’re giving them ’cause intel was nascent and still a pretty new thing in the private sector. So you have to go that step beyond. It sounds like that’s a lot of what you’re saying is more integration, more understanding both sides. What do operators do. What does the intel team do and what does it mean? But also the, a tighter loop of integration. Is that more in line with what we’re talking about here?
[00:06:30] Charlotte Guiney: The tighter integration is a big part of it, and that kind of goes along with the maturity journey of a threat intelligence capability. But at the start of it, I spent like a year just building out our priority intelligence requirements, and I live and breathe and die by PIRs. And I formulate it in a matrix in such a way that we can do automated keyword matching for intelligence collections just to make our lives easier. But It’s a way for us to communicate to the security operations teams, to the GRC teams, to the security architecture teams. We’re able to say, “This is what we care about. These are our priorities and how much we care about certain technologies, certain people, certain, if threat actors or behaviors, based on what we’re seeing in our threat landscape for our industry, as well as our environment,” and getting the agreement with everyone. So when we say, “Hey, this is a PIR7,” everyone knows what that means coming from us, and that’s something that’s a continuous conversation. And in order to get to that holistic threat intelligence level, you have to have that baseline understanding and cooperation.
[00:07:38] AJ Nash: Well,you kind of hinted at where I was going to go next on the questions, right? You talked about this understanding and agreement. So what are you seeing? You’ve been doing this for a while now. You spent a year just on intel requirements, and congratulations, by the way, because most orgs don’t do that, and everything else falls apart as a result. But what do you see as the biggest challenges to moving towards holistic intelligence? And you kind of started us on a path, which is perfect, but what are you seeing as the big challenges?
[00:07:59] Charlotte Guiney: Yeah. You’re gonna probably run into some disagreement as to who owns what. It might be that you have your SOC team already having threat hunting capabilities, and they want to own that. And maybe you don’t wanna step on toes because office politics are still a thing, and that’s never gonna go away, and that’s fine.
[00:08:17] Charlotte Guiney: But you can try to transition and do more of a fusion model so you don’t say, “Hey, we’re not gonna take this away from you, but we’re gonna work on it together. We’re gonna make it better for the overall organization. We’re gonna maybe do more purple teaming, and you can use your SOC threat hunters in more of that capacity.” There are ways to pivot, to play nice, I guess you could say. But beyond that, you’re gonna also run into who owns what within the environment, especially as you start maturing and start incorporating deception or threat research. Are you gonna be able to build safe environments to detonate malware? Are you gonna be able to place those high or low interaction honey tokens or honey pots, depending on what you’re allowed to do? Are you gonna be able to place them in your AWS environment if you don’t have the permissions to even see that environment as an analyst, So there’s a lot you have to consider, and part of that original PIR discussion that I like to have with all of these internal stakeholders, is establishing that relationship so that as we mature and grow towards these capabilities, you already have the groundwork laid.
[00:09:22] Kacper Piwowar: I would imagine, Charlotte, that If you’re gonna start to have this shift over to, holistic intelligence, which encompasses more active engagement, there’s probably a shift of thinking around tradecraft and the importance it has, given that you’re actually actively engaging as opposed to passive consumption, which, tooling tends to kinda solve a lot of that, which is just like getting a bunch of alerts when things are going wrong.
[00:09:45] Kacper Piwowar: But if you start to shift the mindset, I’d imagine that the emphasis and skill set on tradecraft becomes even more important that these people know what they’re doing if they are actively engaging.
[00:09:57] Charlotte Guiney: So I would say I’m gonna answer your question in two ways. Part of that is in building the relationship with other internal stakeholders, I mean other security teams. Understanding that they know they’re doing their job. We can trust that the security architects are handling security architecture, and we can discuss those subject matters. As you’re looking to build out your threat intelligence team for that more holistic viewpoint, coming from a traditional threat intelligence background, What I really look for is someone who is willing to learn and adapt, because ultimately, when you’re doing threat hunting, when you’re learning new skills like building a deception network or doing malware analysis, that’s the biggest thing that I look for, And if someone doesn’t have that, then they’re not gonna go far, I think, anywhere. I don’t necessarily look for specific technical skills. Uh, I look for more of an overall understanding and willingness to adapt and learn.
[00:10:49] Kacper Piwowar: Mm-hmm.
[00:10:50] AJ Nash: That makes sense. I mean, that’s good characteristics, as you said, anywhere, right? The world is a
[00:10:54] AJ Nash: changing place. If you’re leaning on what you did… I’ll use me, right? I was in the intel community for 19 years. I know how to do this, and this is how we do it. Well, all right, I’ve also been out of the intel community for 11 years or whatever, and it’s a different environment to begin with.
[00:11:04] AJ Nash: It’s different objectives, different capabilities, different legal abilities, different operators. I just pointed that out. If you can’t adapt, if you say, “Well, this is how I’ve always done it and this is how it works,” or, “This is the only way to do it,” I don’t think you’re gonna survive in much of any industry, but certainly not in tech.
[00:11:18] AJ Nash: My God, whatever you did five years ago might not exist anymore.
[00:11:21] AJ Nash: I’m curious, and you get a chance to give a positive shout-out to Toyota on this one. You mentioned that you had about a year to do intel requirements, so that tells me you’ve got buy-in from leadership, right?
[00:11:30] AJ Nash: I’ve seen places where people don’t wanna do this, and if they say they will, then they find out it takes time, and time is money, right? It takes energy, it takes effort to build these relationships. You can’t show up on day one and say, “I’m intel, I’m smart. Here’s all the things we need to talk about.
[00:11:42] AJ Nash: Here’s what we’re gonna do.” And you can’t really dictate to people, right? So there’s that, that process you talk about, that relationship-building process. So obviously you have good
[00:11:50] AJ Nash: leadership support on this to get the time to do it right, which is awesome. So the question I have is either, A, have you had an experience someplace where you didn’t have that? If so, then that’s great. We’ll talk about it. If not, can you talk about what it would be like, or do you know others who’ve had that experience and how much different that is when you have to come in and pitch from square one, even if your own leadership doesn’t like it. You know, I’ve seen situations where somebody said, “We’re gonna build an intel team,” but the person you have to convince didn’t make that decision, right? None of them people, you know, it might’ve been the board made the decision, it might’ve been the CEO doing the decision, and now you’re trying to convince the CISO down and none of them believe in this, right? So I guess the first question is, have you been in that environment before? You don’t have to call anybody out by name, but I’d love to hear the experience. But if you’ve been lucky enough not to, maybe you’ve heard of others who have, and can you kind of do a compare and contrast of what it’s like to have leadership that has buy-in from the start and what the value is of giving that time for this to grow?
[00:12:43] Charlotte Guiney: Yeah. I honestly have been in that kind of environment. Not wholly, you know, unsupportive leadership, but more just the priorities were different. And itI was… If I was able to get my work done, I kind of took that time during the week, and just physically sat down with the SOC teams and the red teams and tried to compare what our traditional, priority intelligence requirements, which traditionally are statements, right? Compared to how that and the reporting we’re sending out, is to their daily operations. And I would sit down and I would ask to, shadow what they were doing, and I would compare it to what we’re seeing externally. And that’s kind of how I built this idea of this type of program and the holistic threat intelligence is based on viewing what all the other security teams were doing and comparing it directly to what we were doing in threat intelligence.
[00:13:35] Charlotte Guiney: So it wasn’t so much that leadership didn’t directly support it, I just kinda did it anyway.
[00:13:44] AJ Nash: Got it.
[00:13:45] Kacper Piwowar: Is there like a risk appetite, you think, Charlotte, with organizations that are gonna pivot to this? Like, they need to have a certain type of risk appetite? ‘Cause obviously we see the benefits of it, but not every organization’s like, “Well, you know, we kind of have this traditional capability. We understand the potential risks of it.” Now, if you’re asking them to be more and more proactive in what could be a very dangerous space, do we have the risk tolerance, right? Has that ever been discussed in the corporate setting.
[00:14:14] Charlotte Guiney: Yes, I’m pretty friendly with our legal team here. But honestly, as long as you can assure that you are still incorporating that reactive threat intelligence, that baseline, you know, you’re still producing those IOCs, those defense queries for SOC and IR, maybe just in an automated fashion because, you know, the actual people, the analysts, are pursuing that proactive threat intelligence, that we’re still addressing that initial risk that people want, threat intelligence to address.
[00:14:43] Charlotte Guiney: So knowing that and saying, “We’re not just doing this, we’re building on it. We’re looking at what’s next. We’re looking at how can we better defend the organization, not just reactively defend it.” I’ve never been in a situation, and this is throughout my whole career, where senior leadership has said no to that.
[00:15:01] Kacper Piwowar: Yeah, that makes sense.
[00:15:03] AJ Nash: It does make sense. I agree. So I’m curious, as you’re building these relationships, if you have an established strategy or protocol or order or just some recommendations, like what organizations, internal stakeholders are the ones you would recommend? Who do you start with? Is there a progression? I guess every org’s a little different depending on the personalities of the people there. But who are the core people you have to have to get buy-in if you think this is gonna succeed, and then the next group, the next layer out from that, like concentric circles?
[00:15:29] Kacper Piwowar: Lawyers.
[00:15:31] Charlotte Guiney: I mean, to a certain degree, when you’re delving into deception, lawyers are gonna be involved. But just to get started with that initial documentation of the PIRs and what I call the PIR matrix, you have to get the buy-in from SOC and IR.
[00:15:46] Charlotte Guiney: I would even say threat exposure, or vulnerability management, whatever your organization calls it, as well as your red teamers. Or if it’s also pen testers. Sometimes it’s the same team, sometimes it’s not. Just because they look at security a little differently for your organization, and they know a little bit more about some of the holes. So I initially engaged those teams. I kind of went in with like, “I think this is what we care about, but let’s have all these teams validate it and get kind of their sign-off that they agree this is what we need to care about, reactively and proactively as a, a security organization.” And from there, you can confidently build out those automations to be like, “Okay, we can just feed them what they want,” right? And then build on that. So as you can grow outside of the traditional security operations type of teams, you can start doing more of that proactive work, more of that holistic end-to-end threat research, threat intelligence type of work.
[00:16:45] Kacper Piwowar: Charlotte, during this process, ’cause it’s obviously it’s a lengthy process, any sort of interesting pushback or interesting challenges that you came across? because every organization always has certain teams or certain individuals that are like, “Well, we either don’t wanna do it, we don’t wanna invest there,” or maybe, “This is not a good idea,” or, you know, work politics kind of plays into it. Did you come across any of those scenarios?
[00:17:10] Charlotte Guiney: To a certain degree, there’s always gonna be a level of ownership as to who owns what type of capability. You don’t necessarily wanna take over something that a teammate might already be doing. you don’t wanna stir any bad blood because security definitely does not operate in a vacuum.
[00:17:24] Charlotte Guiney: I think the biggest hurdle that I’ve had to overcome, and we still deal with it day to day, is as you’re pushing towards this holistic threat intelligence, you’re gonna have to start engaging a lot more of non-security professionals.
[00:17:38] Charlotte Guiney: So you’re talking, you know, IT and general engineers, who might not truly understand what you’re talking about at this theoretic level. You know, the threat actors are doing X, Y, and Z, and they’re like, “Okay, I don’t really understand that.” and making sure to not step on any toes in that regard because their cooperation is absolutely necessary a lot of the times.
[00:17:57] Charlotte Guiney: You know, I spoke earlier about you wanna be able to put a honeypot in an AWS environment, but you don’t have any of the rights to do that.
[00:18:05] Charlotte Guiney: You know, maybe you can tell them what you wanna look for, but you’re gonna have to include more people maybe than you want to for a deception capability.
[00:18:11] Charlotte Guiney: But that relationship is absolutely necessary, and there’s always a push and pull between security and IT teams especially. So depending on your organization, that that’s leans one way or the other, I’ve found. And it’s just something that you have to work through, and it’s… From what I’ve seen team by team, case by case, it’s the best way to do it. Unfortunately, it’s just gonna take time to build those relationships.
[00:18:35] AJ Nash: So you don’t want to take this time to call out whoever that jerk was, right? I know there’s one in your head right now. You don’t want to take this moment to be like, “That guy slowed me down.” No, I’m just, I’m just, I’m, I don’t.
[00:18:44] Charlotte Guiney: No.
[00:18:45] AJ Nash: Of course not. It’s a terrible idea. You opened the door to an interesting question. In the process of going through this and building these agreements, you mentioned something about documentation. So how important is it to document all these things? You may have a great meeting, get along and feel like you’ve got some shared understanding of how this is gonna go forward, and either, A, that was one person within a team and many people on the team weren’t there, or B, that person is somebody like me perhaps, and they have 28 more meetings and they’ve forgotten what they agreed to. So how important is it to have all these things documented, to have intelligence requirements documented, to have, you know, sharing agreements documented, to have a shared understanding of motives and objectives? How much documentation do you have on this? How important do you find it to make sure you’ve gathered all these things, follow-up notes in meetings and memos and files and all these kinds of things?
[00:19:29] Charlotte Guiney: It is extremely important to document everything. And I’ve kind of gone back and forth with that, throughout my whole career, and I think I’ve had some managers who, like, live and breathe by documentation, and I’m starting to lean more towards that, to be honest. Really just being able to have that standing place that everyone can go to understand what the concerns are for your organization’s environment. and that’s a place that you can always go back to. And part of that, though, is that I don’t look at any of these documents as static. They’re always changing. They’re always gonna evolve as threats evolve, and that’s the nature of the threat intelligence.
[00:20:07] Kacper Piwowar: So this always comes around and every time we kind of talk about this AJ, I’m always like, “Man, we’re talking about AI again.” But it is important to kind of figure it out in all different aspects because it just has such a huge impact on so many industries and so many sectors and so many job functions.
[00:20:25] Kacper Piwowar: And I wanted to ask Charlotte, what do you see as both the risk and reward of holistic intelligence in the age that we are in, the golden age of AI or its infancy, depends on how you look at it. and is this type of approach truly feasible for small and medium-sized businesses, or is it just reserved for large enterprises?
[00:20:47] Kacper Piwowar: ‘Cause when we take into account, like you mentioned, the effort, the tools, the size of the teams, smaller organizations might just have one person that’s kind of running point, and they’re resource-constrained, and when they think about this, they think of it as like a fairy tale, right?
[00:21:04] Kacper Piwowar: Sounds amazing, but we can’t do that here, right? And so I guess it’s a two-part question, which is the risks and rewards of this approach in the age of AI, and then is this approach actually feasible for the smaller and mid-sized market?
[00:21:18] Charlotte Guiney: Yeah. So for the first part of that question, I look at AI, AI-enhanced threat actors as well as frontier AI, so agentic threats themselves. In the same way I would look at any other threat actor, quite honestly. You’re still gonna be tracking behaviors, whether it’s a human or an AI agent on the other end. Just the speed at which they’re attacking is certainly a lot greater, and the complexity has changed a lot. Maybe the lower priority, like vulnerabilities, for example, are now a higher priority, actually. But at the end of the day, because you’ve documented those PIRs, you’ve built that understanding of, what you care about or as an organization, you understand, whether it’s your crown jewels or high-profile employees, whatever it is you want. As you’re building your proactive threat intelligence program, you’re building for that defensive posture. So you’re not constantly trying to chase the next threat actor, whether it’s human or AI, but you’re building out. That’s how I like to look at it as, you’ve got your crown jewels as an example.
[00:22:18] Charlotte Guiney: You’re placing deception around that. You understand the threats facing that based on your industry. You’re doing that proactive research to look into what those are and working with SOC and IR to ensure that detections are going in, and you’re constantly testing those with purple team.
[00:22:34] Charlotte Guiney: So it’s, it all comes together, and I think whether it’s AI or human, it’ll catch them.
[00:22:40] Charlotte Guiney: If it’ll catch a human threat actor, at the end of the day, it’s still a honeypot. It’s still there. It will hopefully catch an AI one. Just depends on, again, as you… I’ll lead into the next question, uh, budget constraints, right?
[00:22:54] Kacper Piwowar: Yeah.
[00:22:55] Charlotte Guiney: That’s a reality.
[00:22:56] Kacper Piwowar: Down to money, right? How much?
[00:22:59] Charlotte Guiney: There’s a level to it, yeah. I deal with it myself. I’ve always dealt with it my whole career. I’ve been in a team where it was just me for a year. I do know what it’s like. We are in a world where we can use AI to help with some of that offloading of the labor. I talked a little bit about once you get that kind of documented understanding of what your priorities are, you can build some automation. So I really do push that automation, whether that’s working with engineers to build it or using AI to help you, just as long as you have some human in the loop to review it, I’m fine with that. And that’ll help smaller companies get more towards that proactive state. And then kind of harking back to earlier in our conversation, maybe more of that fusion model is what’s gonna work for you. Maybe you don’t, as a threat intelligence team, own th- proactive threat hunting. You don’t necessarily have to own deception. But you can get a group of people together, representatives from different teams, and all work on it together.
[00:23:56] Kacper Piwowar: Mm-hmm. So it sounds like the real barrier sometimes isn’t even size, it’s about the maturity of the team.
[00:24:03] Charlotte Guiney: Yeah, I would say that.
[00:24:04] Kacper Piwowar: Yeah.
[00:24:05] AJ Nash: You bring up some pretty good points about focusing on yourself, right? So that’s the whole point of intel requirements is to understand what you need. Yes, adversaries are a part of this eventually, right? But the goal is to really understand yourself. So I’m curious how far down the path you go in terms of, you know, the CMDB, the Crown Jewels assessment, things like that being in there. Because, know yourself is the first thing, right? Think of “Art of War,” right? Know thyself, and then know your adversary. And, as somebody who is a sports fan as well, growing up, you hear lots of coaches that’ll say, “Hey, I’m not worried about the other team. I’m worried about us.” You know, “We know what we do well. We know what we need to do, and if we do our job, we’ll be fine.” So I wonder what your thoughts are though about, say, like the CMDB, the Crown Jewels assessment, about really understanding yourself. And then as you said, you’re able to build, knowledge that then can be turned into capabilities to defend against known vulnerabilities in systems you already have, and then known vulnerabilities that have already been exploited regardless of who the adversary is, with the thinking being that, you know, AI probably won’t create brand new vulnerabilities.
[00:25:01] AJ Nash: And if they do, you can’t really… You can’t defend against an unknown vulnerability anyway. You can’t defend against the zero day before it happens, right? So what are your thoughts on that though? The CMDB, the Crown Jewels assessment, how that fits in, in that focus on know yourself really well.
[00:25:15] Charlotte Guiney: That fits right into it. I look at the PR matrix that I’ve developed and, I say tech stack, but what I really mean is it’s kind of listing out our crown jewels beyond it to a certain extent of, operationally important technologies, but not necessarily, all hell breaks loose type of technologies for those crown jewels. So having that documented is that first round to ensure that those high priority vulnerabilities, those attacks that are happening out in the wild that do relate to those are automatically being transferred to the appropriate teams, um, that should be taken care of. And you’re able to then do a lot of that work proactively understanding what your environment is, as you said, bring it back to the environment from what’s going on externally. Whether or not you actually have a list of your crown jewels, I know some some organizations don’t, and that could be a roadblock that you have to deal with. I’ve certainly dealt with it before, and I’ve taken it to my role as maybe sometimes it’ll take longer than a year, right? To get those PIRs documented because you don’t have those crown jewels documented. It would be nice if there was, I’m not gonna lie.
[00:26:21] AJ Nash: Sure.
[00:26:21] Charlotte Guiney: Part of that is, again, it helps you build those relationships. You start reaching out, you start trying to see, okay, what are all the teams working on? And you can start forming your own crown jewels to proactively defend against. And so it’s not necessarily what IT would consider crown jewels, but it’s a place to start for threat intelligence.
[00:26:40] AJ Nash: Yeah. So, when we talk holistic, you know, in the government we used to talk about, uh, hardware, software, and wetware. So, hardware and software, then people recognize. The term wetware is less understood. It’s people, basically. So anyway, so we talked a lot, I think, in this about hardware and software, right? We’ve talked in very technical terms, but where does wetware fit in? You know, when you talk about this holistic approach to getting into like, you know, social media management and brand management and, you know, helping organizations protect against social engineering, which obviously is huge. You know, phishing is still the number one way in which you’re compromised. So, you know, working with insider threat teams, for instance, executive, protection teams. Where does that fit into your strategy in terms of, I guess the size and scope of it, but also the timing? Is it something you do early?
[00:27:19] AJ Nash: Is it something you do later after you’ve done the tech? It may be organizational dependent, but where does that fit in for you?
[00:27:24] Charlotte Guiney: That one I’ll say depends a little bit on kind of the direction that senior leadership wants to take security.
[00:27:30] Charlotte Guiney: So you have to be, again, willing to adapt to what your organization wants overall. But I consider insider, I consider EP and, maybe customer protection or, you know, product security, those are all still internal stakeholders. And after I have that initial, security operational buy-in, you start bridging out. I treat them as intelligence customers as I would any other person receiving the threat intelligence.
[00:27:55] AJ Nash: Kacper, do you have anything else you want to add before we close this up? I know we’re running a little short on time, but I don’t wanna cut you off. I feel like you might have had something else going on.
[00:28:02] Kacper Piwowar: I think it’s an interesting concept, and I think it’s something that I’ve heard a lot of discussion about. It’s becoming more and more relevant as the risks become higher, right? So when I thought about this from like an SMB and mid-size perspective, it’s like if you’re not looking at a holistic strategy and you’re strictly being reactive, if something was to potentially occur, it’s a huge risk ’cause your business can go down overnight. If you’re proactively taking an approach, you’re matching the effort with the potential risk that’s involved with it. So it actually makes more sense to think of it differently, not saying, “Oh, we can’t really afford to do it.” Well, it’s like you can’t really afford not to do it because the risk is so high if something occurs.
[00:28:44] Kacper Piwowar: So I think it’s a mindset shift, and it’s interesting to see your perspective, Charlotte, on kind of how you guys are tackling it, because, for the most part, I’ve kind of read about it theoretically. But now that you kind of bring to light the importance of relationships, the time it takes to actually execute on the strategy, the diligence required for it, the buy-in required for it. It’s a Herculean effort, and kudos, that you guys are taking that approach.
[00:29:08] Charlotte Guiney: Yeah, it’s definitely been a journey. I’m not gonna lie. When I first kind of pitched this evolution of threat intelligence, it was theoretical. You know, I had done bits and pieces of it here and there throughout my career, but being able to have the ownership and say from end to end, “This is what we can do, and this is the benefit to the organization.” You know, it’s, we’re still adapting and growing with that because we are working on it day to day.
[00:29:31] Charlotte Guiney: Um, I even had to pivot from proactive threat intelligence to this more holistic end-to-end threat intelligence type of program because of frontier AI. I didn’t have to think about that three years ago. But that’s the world we live in. You’re absolutely correct.
[00:29:45] AJ Nash: How are you measuring success? Or how do your leaders measure your success, I guess? How are you measuring the success of this program now? What are the metrics you have? ‘Cause metrics obviously run everything eventually, especially if you spend money. What have you found that’s been successful in terms of measuring success?
[00:29:59] Charlotte Guiney: So we’re still building things out. It depends on what your organization cares about. Part of it is proactive hunts, security gaps identified, that type of thing. Purple teams that are actually able to come to fruition, and you’re able to pull out security gaps and risk findings from those as well. And you also start to see some of the automated metrics where you get, IOCs blocked and whatnot. So that’s kind of taken care of with that automation. And then moving forward, you’re able to start seeing activity on your deception network based on what you’re seeing externally, so that validation back and forth. And also, you know, feedback from your stakeholders. You’re always gonna get RFIs in any threat intelligence program, and that’s just gonna be a part of it, and that’s a key metric.
[00:30:43] AJ Nash: That’s a good point. Not just bean counting how many RFIs, but how are they being answered? You know,what’s the feedback to that? You know, what is the impact? I know, like you said, you’re still building, so it’s, you know, there’s more time in this, but I know other organizations have talked about at some point you gotta put it in terms of dollars and cents. There’s a business value to this. You know, I’m spending X number of dollars on this intel program and all the things you’re doing, I need to get X plus something, to make that worthwhile, right? If I spent X and I got back half X, then organizations have a hard time justifying the continued to continue to spend.
[00:31:11] AJ Nash: So,I’ll be interested as you’re going forward to see how well you do with that and what, amazing things you come up with, because that’s always been a big challenge I’ve seen especially because a lot of organizations don’t document the connection between the two. We got knowledge, we got ideas, we learned things, we ended up taking an action, a bad thing didn’t happen, and people seem to forget the whole reason the bad thing didn’t happen is ’cause you took that action, and you took that action because the intel team told you to take that action. A lot of times it doesn’t get documented, and then being able to say, “If we hadn’t taken that action, we would’ve been like our neighbor over here who didn’t, and by the way, it cost them X number of millions of dollars.” That’s a challenge to be solved yet, I think for most organizations, and I think if anybody’s gonna do it well, it’s probably gonna be you. No.
[00:31:49] Charlotte Guiney: So far so good.
[00:31:52] AJ Nash: All right. I think we’re running low on time here. Kacper, do you have… I don’t wanna cut you off, otherwise I’m gonna ask Charlotte her last thoughts, but I wanna make sure I haven’t cut you off. Did you have one more on there or not?
[00:32:01] Charlotte Guiney: Yeah. No, no additional thoughts. Just thanks, Charlotte. Appreciate you shedding some light on this, like I said, beyond the theory and what’s actually happening in practice. This has been a wonderful conversation. You know, I really believe in what threat intelligence can do, and I love discussing it with people.
[00:32:19] AJ Nash: Awesome. Any last thoughts you wanna leave the audience with, Charlotte? Advice, lessons learned, I don’t know, weekend plans, whatever it might be, right? Anything you wanna leave as last thoughts, how they can get in contact with you if they wanna learn more about how to be like you, whatever you have on your mind.
[00:32:31] Charlotte Guiney: Yeah. I mean, definitely always reach out on LinkedIn. I do actually look at my messages. But my best advice is when in doubt, you know, talk to people. I’ve only been able to formulate this theory of holistic threat intelligence because I went and sat with the SOC and red team and risk teams and legal teams. So again, truly, those people relationships are priceless.
[00:32:54] AJ Nash: I agree. Couldn’t say it better, and so I won’t try to. Listen, again, thank you for being on the show, Charlotte. Thanks for everything you’re doing for Toyota Financial Services as well. For those listening and watching, thank you. You know, this show is really about the audience and the guests. It has nothing to do really with Kacper and myself. We’re just wrangling cats here. So if you’re listening and watching, we appreciate it. You know, like, subscribe, all those good things. If you don’t like the show, tell Kacper. If you do like it, tell everybody. And please let us know, though. We like feedback. We want to improve. If you know people you think should be on the show, would be a good guest, even if it’s yourself, feel free to self-nominate. We’re always looking for interesting conversations for people that we can learn from and be entertained by at the same time. So feel free to do that. You can find anything else you want about us, authentic8.com, slash Needlestack, or we’re on all the social media platforms. Or you can just reach out to Kacper or myself, through LinkedIn or through email or however you need to find us. So listen, with that, I think we’re gonna wrap it up again for today. Thank you again, Charlotte. Thank you, Kacper, as always for being an amazing co-host. Have yourselves a good day and stay vigilant out there. This has been another episode of Needlestack.