Transcript of https://www.youtube.com/watch?v=K0a7alhLKlA, published 2025-04-22. Auto-generated captions, lightly corrected; the video is the canonical version.

Cybersecurity Lingo Explained: vCISO, PII, and More

those thread actors and hackers are making us have to change the way we do security on a daily basis because they're maturing. So, we have to mature too. So, that often means that we have to change the way that we're securing our company. So, that's why it's always continuous. It's never going to stop. There's always going to be that bad guy out there that makes us have to really continue compliance on that aspect. Gather around as we spill the tea on cyber security. We're talking about the topic in a way that everyone can understand. I'm your host, Gerald Row, giving you just what you need. This is the tea on cyber security, a podcast from

[Music] Trava. Hello, and thanks for tuning in to another episode of the tea on cyber security. Cyber security is full of terms and acronyms that most people don't know or understand, and it can honestly feel like you're listening to a foreign language. So, on this episode, we're going to break down even more terms. And I have my go-to cyber security expert to help us gain a better understanding, Marie Joseph. Hey, Marie, please introduce yourself for our listeners. Yeah, I'm Marie Joseph. I'm a senior security adviser at Trava Security. I help a lot of our customers with compliance specifically. So that will include security certifications and privacy focusing on those. And then yeah, anything security related

too. I also help with like some risk assessments and security specific things because security and compliance are different. But I mean we've talked about that before in other episodes. So yeah, truly my go-to expert. you have the best way of like breaking this stuff down so I can understand it. Exactly. I try. I appreciate it. All right. So, let's go ahead and get into it. So, to keep us organized, I have the episode broken down into sections. And so, the very first thing we're going to cover are all those crazy cyber security acronyms. So, first up, Marie, we have VISO. What is that? So VCISO stands for virtual chief information security officer. So at most

companies, especially larger ones, you'll hear it probably without the V. That's kind of like your seuite level. And those people are really running your data security program at a super high level. And if I'm being honest, like they're usually a very expensive salary. So having the virtual ones gives a lot of businesses that opportunity to not have that salary like in-house and just have the hours when they need it. So having those virtual the virtual consulting in that sense is where small businesses really get a lot of benefit because it's at a cheaper level. They get the help they need at the hours they need because they don't usually need someone that's a full-time staff

because their infrastructure is not at that larger level. Right. That totally makes sense. And just so everyone understands, the V in this acronym is actually a little V and everything else is capitalized. And we do have an entire episode dedicated to this and be able to help us understand a little more of like how SMBs can benefit more, but Marie did a great job at like explaining it already. So, next up, PII. So, this one usually gets into like data more privacy. PII stands for personally identifiable information and it's anything that can like directly or indirectly identify someone. So best examples of this it would be like first name, last name, social security number, place

of birth, biometric record is also one which I think is kind of one people don't think about and like your geographical location. It can also sometimes be like email addresses and phone numbers, but it's kind of like looking at it as if it's a combination usually of a couple of those. And if you combine them, like would you really be able to identify that person? And that's when it becomes PII basically. Some of those standing alone could really identify someone too. And like they're information you wouldn't want some threat actor getting a hold of in any capacity or anyone besides yourself. So that's kind of what that is. Yeah. All right. So, next up, BCP

and how it's different from just an incident response plan, which I'm giving some of it away already. Yeah. All the acronyms. So, BCP is business continuity plan. You most likely, if you've heard of this at all, have heard it in a combination with other acronyms, too. So, sometimes you hear BCDR, which is business continuity and disaster recovery, because they often go hand in hand. So a short and sweet way to look at it is a BCP looks at the bigger picture of keeping operations running in a business while an incident response plan focuses on managing specific security threats and minimizing damage from them. So I always think BCP is more higher level and operational focus

gives kind of like your business leaders what they need to do in some capacity who they need to contact while the incident response plan becomes more specific and sometimes people will put like specific incidents that have occurred or common occurrence ones and like how to act on those. So it kind of gets more technical in that sense. It's kind of different teams look at them, but the CP I would say every team looks at because it kind of involves everyone, especially at the higher level at your company. All right. Yeah, that's helpful. So, SIM, what is that and what role does it play in cyber security? This one always, if I'm being honest, like this

is an acronym that sometimes even I get stumbled on because it just it's it's kind of long. So, it also gets called like a SIM every once in a while too. You'll hear that as how it's said. So it's a security information and event management. Basically this is like a central hub for like security monitoring and like alerting and it can pull in from like other tools you might have or it can be like one own its own solution depending on the company that you get the SIM from or buy from and it collects analyzes and correlates that security data across your whole organization. It's giving that like real-time alerting and real-time response that your

company needs. A lot of people use these to enhance their security program or for compliance specific. All right, so next up is kind of a weird acronym, but dev sec ops. What is that? It is a weird one because typically like you hear them all separately like you hear dev like sec and ops separately because it's development, security, and operations. Okay. So what I like to think about it is like a lot of us work in positions where we wear a lot of hats. So this person is just wearing three hats. So that's what it really stands for. And I would say you often hear like DevOps cuz people don't really focus on security. No

offense to them. It's not a priority in some companies at the time or they have someone else like running the security aspect. So that position just kind of correlates and can like be like the middle person for all three of those operations. And yeah, I think they sometimes leave it off because a lot of development doesn't lead with security in mind. So adding the SEC part really makes sure that they're building their software with that security aspect in mind. Okay. So dev sec ops is like a position at a company. Correct. Got it. All right. So, the last one that I have in our acronym section is BC, which I know is more of a

TRAA term, but this could be for a potential new customer or anything like that. What is a BC? Yes. So, BC stands for baseline cyber risk assessment. You probably typically hear it if you've done anything within your business, just regular called a risk assessment. These are something that need to be done annually. We call it baseline because usually your first one with us is going to be your baseline of your security maturity program. So that's what those risk assessments are doing is it's analyzing your security posture or lack thereof. And then as you go on and do them annually, you should be increasing your maturity posture. And that's what those are really defining. And it's

proving to your prospects, your customers, your auditors, too. Because usually it's you have to do it for most audits. It's proving to them that you are working on your security program when you do enhance that score every year and it gives you goal usually of like these are our weaknesses. We should focus on those. Yeah, that's super helpful. Okay, so next up new section we're going versus. So a lot of these I think are common terms that people hear, but sometimes they could potentially be like interchangeable even though they may be a little different. So, first up, a threat actor versus a hacker. What's the difference? And then why do these terms even matter? So

hackers usually what how you see it is like they're usually a more technical person. So they are the someone that could they could break into your system whether they're hired to or not. So, they have the ability to be a bad guy or a good guy cuz some people do hire ethical hackers, which like they purposely purchase someone's ability to break into their system, which is good to find the holes and the gaps in it. Threat actors, they're more so like could be like an individual or a group with malicious intent. So, it's not necessarily like they're going to compromise your system, but could possibly do it, but they usually aren't as technical as a

hacker would be. In some cases, a threat actor could like accidentally get into your system and not have had that malicious intent or they don't have the technical skills like and just got there or they don't get into it at all but attempted to. That's how they correlate and are different. I did read somewhere where it like explained it where it was like not all hackers are threat actors but all threat actors could potentially be hackers depending on their skill level, which I thought was interesting and that's kind of a nice way to explain it. Yeah. So, I honestly thought that they were the same thing. I was one of those people that thought it

was interchangeable. So, I'm glad I asked this and you broke it down for me. I used to think that, too. And then in grad school, I had a professor that was like, "You need to stop using the word hackers." Like, use threat actors when you're talking about like anyone basically like stop using hackers basically as a whole. All right. Noted. Yeah. Okay. So, next up, again, something else that I might think is a little interchangeable. Firewall versus antivirus. How are they different? And then what can small businesses need these for? Any business needs both of them basically. A firewall is there and it kind of is literally like a wall like a defense wall. So

it monitors and controls network traffic and usually prevents unauthorized access and acts like as a barrier. While an anti virus, it's usually some program installed on your like laptop or end device and it's usually scanning for any sort of malicious software like in like viruses or worms or any other sort of things and it's like actively detecting activity on your system to make sure there's no like bad guys in it or someone trying to get in. So essentially the firewall guards the network and then the anti virus protects like your individual device from internal threats. Okay. Again, I did not know that. very very helpful. Okay, the last set of terms in this section, a

risk appetite versus a risk tolerance. What's this? If I'm being fully transparent, this one also like this one can like be complicated to me too. Sometimes these show up often on like when people fill out like risk registers. So that's when like you review your business and security risks on a annual basis, quarterly basis, whatever cadence at your company. So like a risk appetite is usually broader and more strategic and like the risk tolerance is more specific and they're both related to risk management in some way. So like the risk appetite refers to the overall level of risk organization is willing to accept to achieve its objectives. So it's what they can accept while the

risk tolerance defines the acceptable deviations from that risk appetite and that's where it gets kind of more specific. So it's essentially setting some sort of specific boundary for how much risk you can take in. I would say most people don't put these on their like risk registers but like usually as they mature and become a more mature program then they start more specific with these using appetite and tolerance. Okay. You mentioned a risk register. Yes. What is that? Yeah. So risk register it usually includes like business risks, security risks and those are things where you individually like usually do some sort of assessment and it's things that could impact your business in a negative way.

So it's things you want to look at at a on a frequent basis. One of the big ones would be like fraud. A lot of people like would list that or internal threats like including your people like your people are often a risk so they have the capability like I mean humans are usually one of the one of the bigger factors there and like natural disasters could be one too like that's a risk some people have to impact like depending on where they live those are kind of just examples so it's kind of identifying like hey this could happen we have it documented that it could happen and here are the steps this is how

much of the risk we can accept from that and that's where like the appetite intolerance come in. Okay, next section. So, we're getting into security basics. First up, what is patch management? I think of like a patch as like a band-aid basically as like I could give you like a theory on it. Usually, companies will have some sort of tool monitoring your systems. So, monitoring like your laptop specifically and it's looking for continuous updates on software in your operating systems on like your laptop basically. And then they will push out patches or band-aids when they notice something is like outdated and needs to be fixed because usually when those updates come about usually has like

some sort of security aspect in mind. So companies will push those out to cover vulnerabilities, bugs, performance issues. So the patch management is like kind of working on healing your device in some capacity. All right. Like a band-aid noted. Okay. And then this next term is something that I hear a lot. I'm always like, what is this? Like I understand, but I don't understand. Okay, so attack surface. What does it mean for a business? And then how can a small business manage it? I know it kind of sounds fancy and scary at the same time. In a way, it's harder to visualize when you're looking from like a cyber security aspect because like you can't

physically see most of the attack surface when you're talking about like software. So the way to look at it is if like say you were like living living in a building your whole attack surface is going to be the outside of that building and honestly under and below. So it's the entire surface of that. So like the attack surface from the like software standpoint and where people come from and cyber security includes everything that like you can see like your endpoints like your laptops and like your servers. It can still be your physical office building too. But then when it gets comes to the software, it also would include like that cloud network that's included

and anything that like your data and your customer data touches kind of becomes your attack surface. So like the bigger you grow and expand like all of that becomes your attack surface and stuff you need to work on protecting with some sort of security mechanisms. So think of it as battleground. Okay. Exactly. All right, man. Attack service is like a battleground. Is that what you just summed it up as? Yeah. Yeah, it's like everything you could attack. Like I always like think of it like as like a castle and like the wall around the castle basically and like all of that is where your enemy could hit. All right, man. Okay. We don't want that

to happen. So, yeah. No. All right. So, next section, which I honestly feel like is Marie's bread and butter a little bit. So, we're getting into compliance and strategy. So, what is continuous compliance? Continuous compliance means that you're continuing to upkeep your security program. The best way is like you do become certified in like SOC 2 or ISO for example. You have to continuously monitor all those controls you put in place. I think some people take the aspect of like we got the certification, we hit the finish line, we're done. But no, it does not stop there. You've now developed a whole program that people are counting on you to keep up. So once that

part hits like you have to make sure all of your controls are continuously for the next year and beyond running effectively more so the continuous happens too because security and technology is changing every day. Those threat actors and hackers are making us have to change the way we do security on a daily basis because they're maturing. So we have to mature too. So that often means that we have to change the way that we're securing our company. So that's why it's always continuous. It's never going to stop. There's always going to be that bad guy out there that makes us have to really continue to that continuous compliance on that aspect. All right, that's important.

So, data retention policies, what are they and then why does it even matter for compliance? Those data retention policies kind of set guidelines for the organization to like follow and manage how long they can keep data. So, like keeping the data, storing it, and eventually deleting it. The deleting it is where most people question that. So it's assuring compliance with legal regulations and best practices. So it defines that retention period which data is like crucial and then if they have any like sort of legal obligations that they need to be meeting because like different countries or different companies ask you to delete their data at specific points or like at end of contract like efficiently

managing the storage of the data you consume in like a simpler way and like an everyday way. It's like a policy of like when to clean out your closet. Basically, you have to like look at it like, you know, you're never going to wear those clothes. You've had those same clothes for five years. We might as well pitch him. I haven't touched them. And that's kind of like you take the data like I haven't touched that data in 5 years. It's not applicable anymore. Like it's just get rid of it. And essentially cuz like if you were to keep all of that, you would have to probably buy a bigger place with a bigger closet

or pay for more storage. The same thing comes for data where the more data you keep and store like you're going to have to buy more storage whether it's like a physical server or in the cloud you have to buy more cloud storage. So that's why people also keep retention policies because otherwise they would keep having to buy all the cloud storage. Man, I actually have some things in my closet from like five years ago that I need to throw away. I can't buy a bigger house so we got to get rid of it. Exactly. All right. So what is a cyber security maturity model? A lot of risk assessments use these by the way,

but a cyber security maturity model is usually some sort of framework that evaluates the organization cyber security posture and it will outline different levels of security maturity and readiness and usually is a way to also identify any gaps in your program. So it can range from awareness of like being like a great control that you have in place because it usually will go by controls within the framework then it will focus on like ways you can improve a lot of like more mature programs and like levels that get used in cyber security maturity models is like they go focus on like initial manage defined controlled and optimized so like usually I think of that like

level 1 2 3 4 and five basically you want to like hit the defined one that's like the middle usually like that means you have everything well documented mented and controls well in place. So like you're there like you're a happy medium basically and then you can try to go above and beyond. All right man that was super super helpful. So we know that the cyber security is full of acronyms and terms. Hopefully by the end of this you don't feel like it's as much of a foreign language. Marie I really appreciate the time that you've taken to answer these questions for me. Is there anything else you would like to point out before we

wrap this episode? Yeah, I think the final thing would just be the cyber security and tech world as a whole have a lot of acronyms. I think those sometimes can often be changing too. And I think a lot of people also have different meanings for some of them. So, I'd always recommend clarifying with people being like, "Is this truly what you meant by using this acronym?" Just to have that clarification just because some people like to make them up because there's a lot of them out there. So, making sure it's a common one and that we're all talking about the same thing. Yes, absolutely. Do not be afraid to speak up during a meeting. You

want to make sure that you're understanding what is being discussed. Anyway, that's another episode of the tea on cyber security. Thank you. Now that we spilled the tea on those cyber security terms, it's time to go over the receipts. Marie really covered a lot of information for us during that episode. So, let's go over the main things that I took away. Receipt number one is what is a viso? And Marie framed that as a security expert that is really at the sea level and that helps a company develop their cyber security strategy plus more. And it's easier for a smaller business to obtain a V Sisso versus a SISO which is a fulltime position as

a VISO is more of a contractor and it's hourly making it affordable for those smaller businesses. The next receipt that I have is another acronym which is PII which is personally identifiable information which literally is information that can identify a person. So this is anything like a social security number, an address or even an email receipt. Number three, what is the difference between a threat actor versus a hacker? I honestly thought these terms were interchangeable, but Marie helped me understand that they are in fact different. A hacker is a little more technical and can be good or bad because some companies can hire an ethical hacker. They have permission to come in and figure out

where those weak spots are where a bad hacker can get into a company. And a threat actor can gain access. Sometimes it could be by accident or anything like that, but a lot of the times they do have malicious intent behind that. Another receipt that I have is patch management. And Marie framed that as being like a band-aid for software. So if something needed to be updated or anything like that, patch management is able to patch fix the problem so that hackers can't access it. And the final receipt that I have for this episode is cyber security maturity model. And this helps look at a company's posture and the maturity of their cyber security. It

can help identify gaps to make sure that the company is in good standing and that it is in fact protecting its data. Wow, we really covered a lot of information during that episode of the tea on cyber security. I hope you listener took away as much as I did. Stay tuned for a future episode of the tea on cyber security. Thank you. And that's the tea on cyber security. If you like what you listen to, please leave a review. If you need anything else from me, head on over to Trava Security. Follow wherever you get your podcasts.