
Episode 38 · · 41 min
Betsy Bevilacqua From Almost Lawyer to CISO and Security Leader
VP of Information Security at Chainalysis
Episode summary
Betsy Bevilacqua is the current VP of Information Security at Chainalysis. Initially, she had her mind set on law school until she did a self-audit and realized that she enjoyed computers and tech much more. Her journey into infosec led her to move from Kenya to the US to obtain a degree in Security and explore various companies involved in academia, food and facilities, healthcare, telephone communications, and finance to more traditional tech. Her interview is full of advice for those looking to break in and those already in infosec.Computer
Before infosec: Aspiring lawyer in Kenya, then IT help desk and tech support
Chapters
- 0:00
Intro: Betsy Bevilacqua's path to security leadership
Ayman previews her switch from law, her hiring philosophy and her thoughts on diversity and inclusive language.
- 2:18
Career overview: Chainalysis, Facebook and eBay
Betsy summarizes 16 years leading security teams across many industries.
- 3:26
From almost lawyer in Kenya to computers
She explains why law school was the default path and how she realized she loved computers and games.
- 7:21
Coming to Buffalo and studying information systems
Betsy describes her parents' support, moving to Buffalo and choosing information systems over computer science.
- 13:07
The professor who opened the door to security
A professor who worked with the FBI on cybercrime taught her intro security and sparked her interest in being a defender.
- 15:10
First security job as an incident handler
She chooses a university incident handler role over an anti-money-laundering job and describes the local job market.
- 18:54
Hiring for EQ and guardrails, not gates
Betsy explains why emotional intelligence and influence matter more than raw technical skill when she hires.
- 21:30
Incident response in academia: AOL worm and homegrown NAC
She recounts handling botnet infections, mailing letters to students and building the NetPass quarantine system.
- 25:15
Facebook: FTC audits and security outreach
Betsy talks about joining Facebook after the FTC consent order and the CodePath intro-to-security programs.
- 29:18
Mentorship, apprenticeship and moving from audit to GRC
She shares mentor stories, advice for finding mentors and tips for auditors moving into technical roles.
- 38:09
Inclusive language in security
Betsy discusses terms like master-slave and black hat and why language matters.
- 40:10
Closing: Ayman's new community
Ayman asks listeners to check out his new community in the show notes.
Key takeaways
- If you are in a field that does not fit, do a self-audit of what you actually enjoy, as Betsy did when she left the law path for computers.
- A computer science base (even two years) gives security people a better foundation in data structures and algorithms, though an information systems degree adds business context.
- When hiring, look for passion, emotional intelligence and the ability to influence people with data rather than just saying no.
- Mentorship works best when you ask a specific question; 'micro mentorship' via communities such as WiCyS or Blacks in Cybersecurity is better than a vague request.
- Auditors who want to move into technical GRC roles should use training budgets and seek technical projects, or take core CS courses or boot camps.
- Be conscious of legacy language in technology and security, since words can affect people entering the industry.
Notable quotes
I did a self-audit very early on, and I realized that I had made a mistake.
they start off as technical problems, but then you dig deeper and you realize humans are kind of human. So we've been in the business of debugging humans.
you have to do the work first. You have to decide what it is that you want to get out of a mentorship relationship.
Questions answered in this episode
- How did Betsy Bevilacqua get into cybersecurity?
- Betsy planned to study law in Kenya but realized while waiting for exam results that she loved computers. She moved to Buffalo, New York, studied information systems, took an intro security class from a professor who worked with the FBI, and became a university security incident handler.
- Is a computer science degree better than information systems for a security career?
- Betsy says computer science gives a stronger base in data structures, algorithms and thinking, while her information systems degree helped with business context. She recommends at least two years of CS if you are interested in security.
- How should you find a mentor in cybersecurity?
- Betsy suggests joining free digital communities such as WiCyS or Blacks in Cybersecurity and asking one specific question rather than asking for a general mentor. She says people are often generous if you share what you want to do and have done the work first.
Show notes and links
Show the original episode notes
Betsy Bevilacqua is the current VP of Information Security at Chainalysis. Initially, she had her mind set on law school until she did a self-audit and realized that she enjoyed computers and tech much more. Her journey into infosec led her to move from Kenya to the US to obtain a degree in Security and explore various companies involved in academia, food and facilities, healthcare, telephone communications, and finance to more traditional tech. Her interview is full of advice for those looking to break in and those already in infosec.Computer
https://gettingintoinfosec.com/betsy
See omnystudio.com/listener for privacy information.
Mentioned in this episode:
Full transcript
Transcribed from the episode audio. Spoof ads (Ayman's parody commercials poking fun at the industry) are marked.Download .txt
So I realized that I had an app and I was always the kid who wanted to learn a lot more, learned how to hack our phone system and go right to the PBX exchange outside. And it was just, I realized that's where my passion was.
Welcome to Getting Interned for Sec. I'm your host, Ayman Elsawah. My guest this week is Betsy Bevilacqua. Betsy is a CISO and amazing security leader who shares her story on how she got into security.
When you take these large national exams, you have about three months to wait for your results to come out. And it was during that time I really started pondering, you know, what does it really mean to be a lawyer? What does it mean to be in the legal profession? And the more I dug into it, the more I realized, you know what, actually, I love computers. I love video games. It's almost like I did a self-audit very early on and I realized that I had made a mistake.
Betsy shares with us some of what she looks for when hiring in information security and how the industry still needs to adapt.
So the idea is always looking for, one, is there passion? Is there an interest? Because security is not something you get into lightly, as you know, right? We basically, we take on a lot of risk. It's very stressful at times, but it's also very rewarding. And so I've always taken the point of if somebody has these qualities and they have transferable skills, you can very easily solve a lot of these problems with people who think differently.
As an African-American woman and someone well-versed in emotional intelligence, Betsy understands diversity and inclusion issues well, including those affecting African-Americans and Blacks.
What does this language do to your psyche? Because I remember the first time somebody said master-slave and they were referring, I think it was a database or something. And I remember being taken aback and I was like, wait, what? And then all of a sudden it just became so commonplace that I started using it.
Betsy's an amazing human being and we had a wonderful conversation. So check it out. All right, on to the show. Hi, Betsy. Thanks for coming on the show.
Thanks for having me, Eamon.
Yeah, I've been waiting to have this interview for quite some time, so I'm very excited about this. For those out there that may not know you, can you tell us a little about what you do today and some of your previous roles?
Sure. So again, my name is Betsy Bavalaqua and I'm currently the VP of Information Security at Chainalysis. Chainalysis is a blockchain security company. Prior to Chainalysis, I've been in the security industry for probably around 16 years, which sounds crazy for me to even say that out loud. It's been an interesting journey. I've led security teams at a medical device startup, Codafly. I spent almost five years leading a few security programs and teams at Facebook and before that at eBay, before that health insurance, academia, and a food and facilities company. So I've seen the rainbow of all manners of security programs, starting from when security was slapped on a firewall and some antivirus and called it job well done to where we are today, which is a completely different environment.
Yeah. So lots of experience there and which makes you the wonderful leader that you are today. So thank you. Yeah. Happy to bring you on. So I'd love to get into it. How did you get into infosec? I think from our other conversations, infosec was not your initial career choice. Is that right?
That's right. It was not. So I thought I was going to be a lawyer. I'm originally from Kenya and the law degree is actually the first degree. So meaning you could go right from high school into law school, unlike here in the US. And it's also not easy to get into, right? You have to get certain grade levels and then you apply and it's a kind of rigorous process. So When I was in high school, you know, it was, you know, law sounded cool, lots of interesting problems to solve. And it was either that or med school and I couldn't deal with the idea of cadavers. So that was completely off. So yeah, so anyway, I do all this hard work, pass all my exams or get accepted into law school. And I realized that this was not for me.
How did you come to that realization? Was law school something your parents drove or was it something you wanted? And then how did you come to that realization?
That's a good question. My parents really didn't drive. They did a good job of letting us decide what we wanted to do.
Okay.
And so law was a very, still is a very prestigious occupation. And so when you think about your future, you look around you and the people who are successful around you. And for me, folks in the legal side were, seemed to be doing well. I said, well, that's what I want for myself.
Yeah.
But then we'd only have a break in Kenya. When you take these large national exams, you have about three months to wait for your results to come out. And it was during that time I really started pondering, you know, what does it really mean to be a lawyer? What does it mean to be in the legal profession? And the more I dug into it, the more I realized, you know what, actually, I love computers. I love video games. It's almost like I did a self-audit very early on, and I realized that I had made a mistake.
Okay.
Yeah.
So this is after you took the exam to enter law school, right?
Well, the good thing is it's a national exam that everyone has to take. Oh, okay. It's not based on your grades and they say, yep, you qualify to go into law school. So it was during that process that as you finish the exam, you wait for the results. And then once those come out, then they tell you almost at the same time, whether you were able to get into the schools of your choice or the programs of your choice in the public university.
Okay. So you had this free time and you realized that computers was something. Did you grow up with computers when you were little? Like when were you first exposed? How did you come to that realization?
Yeah. So I went to a public-private, sort of like a charter school in Kenya.
Okay.
And they happened to get a grant. It was probably in like the late 80s. They got a grant and they bought a bunch of computers. And they were one of the first few schools in the city to have a computer lab.
Okay.
So we had computer class, but really at that point, computer class was 45 minutes of theory and it was our teacher doing his best to teach us the basics of programming. But the only thing we were excited about class for was playing games because we would then get 45 minutes to play games. It was on a Commodore 64 basic, and we were playing this game called Wizard of War. And we would take turns, and we had about five computers. And so in a class of about 40 kids, there would be eight people assigned to one computer. And I always went first, but then that meant if you were in my group, you never got a chance to play because I got pretty good at playing this game.
Nice.
And so they would just sit there and watch me play. And getting increasingly annoyed or getting increasingly excited because I kept going from a higher level to another higher level and unlocking new ghosts.
Did you have a crowd behind you at some point?
Oh, yeah. Yeah. It was like Twitch, you know, but just back in the day.
That's so funny.
Yeah.
Okay.
So I realized that I had an app and I was always the kid who wanted to learn a lot more, learned how to hack our phone system and go right to the PBX exchange outside. And it was just, I realized that's where my passion was.
Okay, that's cool. That's awesome. And so now you've taken this exam and you're waiting for the results and you realize computers is something you want to do as a career. What are some things you did after that?
Yeah, so it was again, like one of these, I love computers, but I don't know what I can do. And at the time, looking around the courses that were available were the certifications for Microsoft. So there's MCSE. Solutions engineer, MCSD, solutions developer. They were very expensive. I mean, the books themselves were, you know, just at that time in my life, something that I would probably have to work for a year before I could even afford that book. And so I started doing some research on what programs were available in Kenyon at the time, not as many for computers or computer science or information systems. And so I would spend a lot of time in internet cafes because we didn't have internet at home.
I would just look at various courses. And I realized that the U.S. had a number of interesting paths for people who were interested in computer science or just information systems in general. And so I started working on the campaign with my parents that I wanted to one day go to the U.S. and take a computer course.
Okay.
And so they were always very supportive.
Okay.
Yeah. I mean, they didn't get it, but they were supportive. Oh, okay.
Wow.
That's awesome. So my dad, through his work, he was for a long time in the medical device business. And he had some contacts in Buffalo, New York.
Okay.
And he said, I have a friend in Buffalo, New York. All I heard was the New York part, by the way. I didn't really pay much attention to geography at the time. Okay. He says, I think we can organize, we can afford to send you there for a month and then you can figure out how you're going to pay for your schooling. Well, number one, if you can get in and then pay for your schooling. And I said, fine. And so he talked to his friend and his wife and they said, yep, we'll host Betsy for a month and she can do some tours and all that good stuff.
Cool.
And that was really the path that opened a door for me because I ended up in Buffalo. And the folks who know Buffalo out there, it's a wonderful place to go to school because it's extremely cold. And coming from a warm climate to a cold climate, being indoors meant I could focus a lot on my studies. And I ended up getting an undergrad. I started off in CS, but then changed my mind midway because I was interested in information systems because it offered a broader set of courses that I was interested in. So it was a little bit of programming, a little bit of database work, and then the business courses, which I was also interested in. How you can apply technology to solve business problems. That's really where my mind was going.
Okay. So today, information systems compared to a computer science degree, what are the trade-offs today versus back then? Or what are the trade-offs today for those in college and looking for college as a career path to technology?
Yeah, so I think today if I was inviting someone, and I do advise people trying to get into the field, that I still think that CS will give you a better base because if you look at where we are today and the problems we're solving, if you have a good understanding of data structures and algorithms and CS teaches you how to think. And also it gives you a good base for, even if it's just very simple programming. So, you know, I find having to do a little bit more extra work than if I had already a CS degree. But at the same time, from a business perspective, if somebody gives me a financial statement, I know exactly what's going on there. So, you know, it really depends on the path that you want to take.
But I still always say if you can at least even do two years of CS before you branch out, if you're really interested in security, it gives you a good context into solving a lot of the issues we see today.
Okay. That's helpful. So you did information systems or manager information systems as an undergrad?
Yeah.
Okay. And then did you go straight to the private industry or did you continue with like grad school or anything like that?
Yeah, so right after undergrad, I went to work at a cable company. So if you're an international student in the U.S., back then you got a year after graduation to work in your field. And so I opted to find some work just so I could see what the real world was like. And I found myself definitely either going to banking at the time anyway, or healthcare. These are the major industries. And then there was this company called Delphia Communications.
Okay.
I was able to get a job at Adelphia as a technical support representative. Basically what that meant is I got to learn a lot about internet infrastructure because I'm the person you called when your cable went down and got to spend a lot of time talking to people. But we also had opportunities to work with the field techs and do write-alongs. And I really got a good education there on what it takes to provide internet and to bring that into people's homes.
Okay, that gave you a lot of real experience. What was your role? Like, were you technical? Were you in security at that time? Or just kind of doing basic IT at that time?
Oh, yeah, this is basic IT. Okay. And I should mention that when I was in college, I also worked in the IT department. So I was a help desk, I was building labs.
Okay.
So I always had a computer job. That was pretty much how I paid for my meals.
Okay, that's really good. That's a good base, like from an experience perspective, really good base. So what did you say?
Yeah, it was a lot of fun. I mean, I used to push carts with the all-in-one Macs. I don't know if you remember those.
Yeah.
I got the chance to replace some silicon graphics machines in the CS lab.
Oh, nice.
Yeah, so I learned how to ghost machines. I also learned what viruses can do in a university once they hit the network.
Yeah.
Yeah. So lots of interesting times there.
Yeah. Lack of segmentation back then.
Oh yeah. Or even a knack, right? Like what is network access control?
Yeah. The dorm network connected to the lab network. Okay, cool. And so how did you actually transition into security?
Yeah, so as part of this MIS program, I got to meet, and by the way, I should add, you know, I worked for a year at this cable company, and then I went back and got my master's, I got an MBA. Oh, okay. But within that time, I met a professor who was working part-time for the FBI working on cybercrime. And she was also writing a book on security. And the more I got to know her, I took a few of her classes and I was really interested in what is this security thing? And it's almost as if I'm sitting in class one day and it just clicked. She started to talk to me about trust and confidentiality. And these are things that I had thought of, but never really applied them or even thought about how they would apply into people who are building companies or building systems.
And I remember almost getting goosebumps going, wow, all this sounds amazing. And just the idea of being a defender really attracted me to this field. And that's basically all it took was getting my eyes opened by this professor.
That's amazing. This is during your MBA. Is that right?
I met her towards the end of my undergrad and because it's a small school and I was always living in that community. So we can say it was between undergrad and the grad time.
Okay. And was she an actual professor? Like how did you end up in that class or was it a guest speaker?
Oh, no. Unfortunately, she's no longer with us. She passed, but she was a full professor.
Okay.
In fact, she was at one point the head of the department.
Okay. Was the whole class like security related or?
Yeah.
Okay.
She taught courses intro to security.
And was it an optional class or required? It was optional. Optional.
Yeah.
So you just happened to have taken that class.
I just happened to have taken it. And back then, nobody was really working on security classes.
Yeah. Yeah, that's amazing. I mean, the Goosebumps story and being a defender is like something I hear constantly where someone has just opened up and like, oh, I didn't know this was possible or how it applies to the real world. Many of my previous guests and just folks out there. So that's really exciting. I'm actually getting goosebumps right now. Just thinking about it. And so you got this opening into this world of security and you kind of want to like, oh, how do I get into it? I'm assuming, right?
Oh, yeah. So it was at that point, it's like, how do I do this for the rest of my life? Nice. Again, back then, nobody was really hiring for security folks. So I get this MBA and then I'm like, okay, what do I do now? And I started applying and I was very close actually to getting a gig at a bank, one of the large banks doing AML, anti-money laundering, which I find it hilarious because... Industry I'm in now.
Yeah.
But I had two choices. Go work in the email industry or go and work at another university. So University of Buffalo as an incident handler.
Oh, interesting.
Yeah. And I said, well, the anti-money laundering thing is cool and all, but I'm going to learn so much more going to this university. And also just the fact that there was room for growth in different parts of security, which by then I started gobbling up all this information about the field.
Mm-hmm.
When I looked at the path, I said, I've probably learned more working on incidents. So that was my first official job in security was a security incident handler.
Oh, okay. So you went that route.
Yeah.
How did interviews go then? How was the interview for that position and other positions at that time for security? Did you get any rejections and maybe walk us through some of those wins and losses?
Yeah, so for the bank, it was a fairly, I would say, easy interview because they were looking for people they could train. You might know a little bit about anti-money laundering controls, but for them, it was, we'll get a bunch of grads and we'll walk them through this path. And the work was very structured. On the security incident handling, and by the way, it's not like there was a plethora of jobs that I had interviews for. It was a pretty tight market at the time.
You were staying in Buffalo. So, I mean, I don't know if the job market in Buffalo was, were you applying locally or nationally or?
Only locally. So at the time I wasn't thinking about leaving Buffalo. Okay. So my search was very much focused. And in Buffalo, there's, I mentioned academia, there's healthcare, biotech, there's of course the banking. I think Yahoo had a bunch of, and maybe still does have a bunch of data centers.
Mm-hmm.
But we're talking, you know, this is a long time ago. Yeah. So yeah, so I would apply in a lot of the jobs, like the help desk job. So there's a lot of IT jobs. So if I wanted to be a sysadmin, this would probably have been much easier. If I wanted to go work in insurance, this would have been much easier. But I was very focused on getting a security role and then a security role and in Bufflin that married my possibilities. I even randomly reach out to recruiters and they would say, well, is 10 IT help desk jobs? And I'd say, nope. So, yeah. So the interview process for this particular role, because I had already worked in the academic setting. So I went to Canisius College and then I was applying for a job at the University of Buffalo.
And a lot of the challenges that I saw when I was working work study program, you know, told you about the labs and working in the help desk. All of that was very applicable to them, obviously. And they said, yeah, absolutely. You know, you should come work here. So it was a very easy process, at least for that particular role.
Okay, and that's good. I mean, actually, that's a common thing for a lot of industries, actually, I've noticed, even as a senior person, when going to like, say, healthcare, and like, oh, you don't have any healthcare experience or health industry or medical device experience. And same with universities. So it seems like a lot of these positions want to see some similar background, even back then seemed to be the case.
Yeah, you know, again, I was entry level. So sometimes when you're hiring entry level, you want to make sure that the person won't require too much handholding because when you are starting a job, there is need to provide folks a lot of guidance. And sometimes depending on the size of the team, if the hiring manager doesn't necessarily have the cycles to grow someone, then they're probably looking for who can ramp up quicker.
Yeah. So let's jump around a little bit. So you as a leader right now, what are some things you look for when hiring someone?
For me, what's really important is EQ.
And what is that?
Emotional quotient. Of course, IQ is important.
Yeah.
But EQ for me is paramount. And part of the reason why I bring this up is in the roles that are in the industries we are in today and just looking at where security is headed, it's really important to have empathy for the teams that you're working with and supporting.
Mm-hmm.
So for me, I look at it as if you already come in with the correct attitude around how we coach people, how we, I love Netflix's approach of guardrails, not gates. I really buy into that because I think you can build a really strong program with that. That as a context. So in any of my teams, I always look for people who are willing to use the word no sparingly and to help advise people, provide people the data that they need to make a good decision. But that means you have to invest a lot in teaching. You have to invest a lot in influencing. And that's not always easy. That's the hardest skill to hire for versus going and getting the top Contestor or Reverse or whatever technical background we're hiring for.
I saw a Twitter post about hiring 10x engineers. And then people are talking about how these 10x engineers are often some of the not so favorable people in the office. And they may not, but they're just not really nice people in general. Of course, make in general.
Yeah, it's really hard. I mean, sometimes you can fall into that trap of looking for somebody who's just amazing at their job that nobody wants to work with them. And so then the question is, are they up leveling themselves or the rest of the team, especially if you're in a small company or a small team, you want someone who's going to connect the organization and not just focus on one particular thing and not have influence there. Or even have a negative influence because at that point, building up a team morale can be really challenging.
I think there's a phrase that you use that I love where you're dealing with humans that they're technical, but what is it that you said?
Oh, was it we're debugging humans?
Debugging.
Is that the word?
Yeah, that's one of my favorite things I've heard lately.
Oh yeah. Oftentimes the problems we're dealing with are, yeah, they start off as technical problems, but then you dig deeper and you realize humans are kind of human. So we've been in the business of debugging humans.
Yeah. So where you say, this person might be smart, but I don't want to deal with debugging this person, treating one problem for another.
Yeah.
That's interesting. So now you're in incident response. This is your first real cybersecurity role. Tell us how that was like.
Oh, you know, one, just shout out to the people who are living and working in IR. So all the SOC analysts, people carrying around, we don't have pagers anymore, but you've got the app on your phone. I mean, it was interesting. So at the time, AOL was a big thing on the college campus. And we watched, there was one time we watched the AOL warm just take over our network. Oh, wow. We had instances where, because it's a public university, we would have people come in and connect online. They're machines that are living lives of crime because they're part of a botnet and they don't know, you know, the people who own the machines don't know that. And I would have to be the person to send them a note and say, hey, you need to get off my network because we need to fix this infected computer.
So it was a trial by fire because we didn't have processes built out yet. So as an example of what some of the things we would have to do is if we identified a compromised device, we would have to hunt down the person. But because this is a public university and at the time, I don't know why we weren't using email, but we were actually, I was doing mail merges of letters and then I would have them delivered by the RAs. Oh, wow.
Yeah.
It was crazy, right? And so this is how we were doing containment. And then after a while of this, we ended up growing that team, our team, and we hired a security analyst. And between the security analyst, myself, as the incident response, and I think there were two more people involved, the networking team, we started looking at building a NAC, a network access control, like a homegrown NAC.
Oh, nice. Okay.
I think about this now, and now, I mean, these are products that are available on the market. Cisco, I think, has cornered that market. But anyway, so we built this thing, or the network team built this system called NetPass. And the idea was you would connect your device. It would put you in quarantine. You would have to get scanned, and that would, at the time, we were using Snort. Okay. And then we were, because we're a heavy Windows community, I would work then with another Windows sysadmin and we would look at the largest phones. And then, you know, we would pick which ones we cared about. I think we also included a botnet scanner. But anyway, so you'd go into this, you know, jail, your device would go into this jail and you'd get scanned and then you would get a pass, meaning that you'd get out of quarantine.
Mm-hmm.
And there were times that the switch would fail. There were some upgrades that needed to be done. So it didn't always work. It was really, really buggy. But we actually saw good results out of that. And at the time, I didn't realize that we could probably just have done this easier by going to purchase a solution versus... Spending all the time we did to build it. But I learned a whole lot through that experience. And most of what I learned was around how to communicate to people about what was wrong with their devices and then how best to fix them. So we ended up getting a partnership with the campus bookstore where people could go in and, you know, take my letter with them and they would be able to get help, which oftentimes just meant re-imaging the boxes and we were fine.
Oh, okay. The bookstore had IT people? Is that what I understand?
It's the campus bookstore, but it also was, you could buy like computers from there or you could buy your software.
Gotcha.
Yeah.
That's cool. So your IT help desk experience kind of helped you with kind of coaching people and remediating their security. And I guess you built up some EQ in that, I guess, right?
Oh, yeah. I mean, we're talking about college kids, so.
Yeah.
Lots of patience involved.
Yeah. So if we fast forward, I think you spent quite some time at Facebook. Tell us about how you helped evolve maybe the security program from when you entered to when you left, or is there anything you could share in that regard?
Yeah, so some of the things I can share, I was brought in to Facebook after, and this is public knowledge, so Facebook signed what is known as a consent order from the FTC, which basically means that for the next 20 years that Facebook would be required to undergo a number of audits, security audits, as well as provide the results of these audits to the FTC. But at the same time, Facebook was also looking to roll out its workplace product, which is Similar to Slack. And so there were a number of activities going on that meant that for the first time that Facebook would be under a lot of scrutiny from auditors and regulators. And the team was fairly small when I got there. The security team was small, but also the risk, people focusing on risk and compliance and sort of
How do you translate all the controls you've put into place into something that is into a narrative that is centralized and that also we reduce the load on our engineering teams due to audit? Because it wasn't just auditors coming in. We also had regulators coming in from the payment side of the house because at the time Facebook was launching, you can send money on Messenger.
Okay.
Yeah. So there was a lot of activity going on and brought in to work with the audit team and work with the engineering team and work with the privacy team. So lawyers as well, because we were also looking at Privacy Shield. This is right when, what is the, I'm forgetting now the name of the law that was struck down to replace Privacy Shield. Safe Harbor. So Safe Harbor was gone. And now there's all of these controls that we put into place that we have to build out and work with multiple groups. And I just loved this kind of work because it meant that I got to spend a lot of time with not just security engineers, but also our product. So people who are building out very nascent versions of features, or even if we're working on an acquisition, helping that acquisition come in and understand how to build on top of the Facebook stack.
But from a security perspective was really interesting. So I got to have a hand in a number of those programs, but I think reflecting on my time there, the work that I'm most excited about was the work that touched people in the sense, by people, I mean the next generation of security professionals. So yeah, We were really fortunate to be able to have a program, an outreach program, which in my last years there, I ran an amazing team of very dedicated people who worked to build out programs, underserved communities. So as an example, we would go to universities in rural areas, we would go to historically black universities, and we partnered with a group called Code Path. And, you know, these programs are still in place today.
Mm-hmm. And we piloted a course, Intro to Security, but mostly on application security side because that's where we saw some of the gaps within the industry. Yeah, so people would go to CodePath or CodePath would teach these courses on-site in these campuses with a high population of underrepresented minorities or even people just going to university, the first people in their families to go into university. And we would pull from the CS programs And we worked with a few professors who offered this course as an elective. And so on the one hand, you got to take this course and you would get course credit. But also, we were then opening your eyes to the world of security. And even today, we have people who are working at Facebook who went through this program.
And we have people working at some of the larger companies that you would identify who are graduates of this. Yeah. When I think back, if I ever get another chance, and I probably will focus on this at some point, is opening the doors, similar to how somebody that professor I told you about opened the door.
Yeah, that's a great segue. Tell us more about mentorship. I think you've had some interesting mentorship experience. And just tell us about mentorship in general in the security community and some stories of successes and what you've had to do or what you've done.
Yeah. Yeah. Yeah, sure. One of the things that I noticed was being in security and I got in fairly early. So we're, you know, we're talking 16 years plus at this point. And starting out, when I think about how I attribute my success, it wasn't, yes, of course, I did the work, whether it's studying or at the time it was CDs and buying the books and just, right?
It's like the dark ages compared to now. Yeah.
I know. My mind is so blown when I'm like, I can just get a VM. I have my own AWS instance. Right. And I can go in there and play. This is just crazy. It was either too expensive or just not possible.
I mean, there's even free websites you can launch a VM and just play with, with no anything at all, no software, just a browser. I mean, like on YouTube videos. I mean, we were literally in the dark ages, you know, trying to... Find security information. It's just wild. It's wild. Yeah.
Yeah. So I did the work, but I also had lots of mentors, people who were very, very generous with their time. So when I left the university, I went to go work at a food and facilities company. And I was a security analyst at that point. And one of my job responsibilities was firewall. I was a firewall admin. And I had taken a few courses, but getting into this job, it's not like I can just go in and start making changes in fraud.
Right.
Without much guidance. I'll never forget I had my colleague was a security engineer. I mean, you know, he had been in the industry for a while, but he came out of networking and then got into security. And he basically took me under his wing and he taught me hand to keyboard at the time it was checkpoint, how to change firewall rules and how to configure switches. And when I think about that today and that sort of apprenticeship, without that, I probably wouldn't be where I am today. And I have many other examples of also learning from people when we were deploying PGP, whole disk encryption, to a very large organization of about 7,000 people. And that was my project. Oh, wow. Yeah, I was one of the two engineers who were deployed to that program.
So it's just, you know, I think back and I can attribute a lot of that to the generosity of people and I've never forgotten that. And so when it comes to mentorship, I take it seriously because one, I mean, we keep talking about this shortage of talent and it is real because it's really hard to hire. But at the same time, we have on the other side people who are very much willing to learn if somebody gives them a chance. Or we have people who have skills that are very useful for security. So as an example, I worked with a really brilliant lady who came from the public policy world and she had an interest in security. And through a number of mentorship and coaching, she was able to get a role working on security awareness and now is leading security awareness for a very large tech company.
I also have another story of another lady who came from network engineering and is now a security program manager for another large tech company. And so the idea is always looking for, one, is there passion? Is there an interest? Because security is not something you get into lightly, as you know. Basically, we take on a lot of risk. It's very stressful at times, but it's also very rewarding.
Mm-hmm.
And so I've always taken the point of if somebody has these qualities and they have transferable skills, you can very easily solve a lot of these problems with people who think differently from you. Because I think sometimes in security, if you've been in it for a while, it sort of becomes like a tribe. And then you all think the same way.
Yeah.
Why are we still in 2020 worried about password reuse?
Right.
The fundamentals, like something needs to change. And I think that we're going to get there by inviting more people who think creatively about some of these challenges.
It's like diversifying the gene pool, right?
Basically, yeah.
If you don't diversify, you're going to end up with bad results.
Yes, and we don't want bad results. We're already suffering.
Yeah, that's pretty cool. So these mentors, were they people in your workplace already that you went to seek out?
Yeah, so there are two that I've talked about were people in my workplace. But I also, once in a while, when time allows, I do have people who reach out via LinkedIn or through mutual connections. Especially, I get a lot of questions from folks who are in audit and are trying to figure out the best way for them to move into more technical roles.
Hmm.
That's something I've noticed, especially over the past three years.
And what would be your advice to them?
My advice to them is normally if they're in a large organization to make use of the training budgets that are available and then partnering with more technical teams or working with their managers to get more assignments or projects that would expose them to the more technical side of the house.
Mm-hmm.
And also the folks that I'm referring to coming out of audit are looking to get into GRC roles. And I've noticed over the past two to three years, it's been my experience, we've moved away from this idea of audit just being a checklist or GRC as being a checklist. You really have to have that context now to be able to make recommendations, whether you're dealing with risk assessments, Or this idea of compensating controls. It's not just so you can just throw these words out there without some guidance for a lot of the engineering teams. And so a lot of these roles now require you to have that technical context to be able to help guide these conversations on both sides. That's really where I advise them.
If they have more risk appetite or more opportunity to rebrand themselves or transform themselves, then it's go back and get some core courses under your belt from CS. There's lots of boot camps now that are not as expensive and can probably be done part-time or in an accelerated fashion to give you that boost that you need for that next role.
Mm-hmm. That's cool. So how does one seek a mentor out there? Like, I mean, not everyone can be available from the mentoring side. Not everyone is able to be a mentor. What are some things that you would recommend? Because there's a lot of people out there that are looking for mentorship. And so what are some suggestions for them to find mentors to help them?
Yeah, that's a good question. So I think today more than ever, there's a lot of groups that people can join and you don't even have to be there in person. I mean, we're now all mostly confined to our homes, but there's lots of digital communities. One of my favorites is WISIS Women in Cybersecurity. There's Blacks in Cybersecurity. There's a number of communities that you can join that don't cost money where you can network and The idea of mentorship, it doesn't have to be something where you're building or you're investing so much time with someone. You could have the micro, I'm just calling it this, you know, the micro mentorship where if you have a specific question that you'd like to get answered, that you approach someone through those networking channels and just ask that one question.
Because that's the other piece. When people approach me, they'll say, well, can you mentor me? And I say, well, what specifically is it that you're looking to do?
Mm-hmm.
And they don't know. Right. And I say you have to do the work first. You have to decide what it is that you want to get out of a mentorship relationship.
Right.
And then zero in on that because it could be that you have a number of people who can help you. It's much easier if you're coming to ask me a very specific question versus if you're coming to ask me a number of questions to work with you to identify. Right. It maybe sounds harsh, but at the end of the day, even the people you're approaching as mentors, they probably have a number of other competing priorities and they can't always extend the energy. But if you can at least just get one or two questions answered that will take you down a specific path of more self-discovery, then that's better than nothing.
Right. That's exactly right. Yeah. And then there's groups, right? So you could try groups out there searching. If there's one particular person that you think can get, you know, then that's like the one-on-one then asking a focus question. So yeah, different escalations of right mentorship out there, right?
Yeah.
From crowdsource to the individual, right?
Yeah. And I think people are pretty generous with, I mean, I guess it depends on the digital communities we're talking about, but I even see people on LinkedIn who will just, if you share what your dreams are.
Yeah.
That people are willing to just help.
Yeah, absolutely. LinkedIn, Reddit, Twitter, 50-50. But there are a lot of communities out there that you can post a question and get a variety of answers and just take one of those answers and run with it. Yeah, that's great. Is there anything you want to talk about, like diversity and inclusion or anything like that, that we didn't get to talk about?
One, I love that right now we're in fever pitch with this message of diversity and inclusion. And actually, something that I saw this morning that really warmed my heart was we've started seeing discussions around the language we use in technology today.
Mm-hmm.
And somebody said, it was in a Slack thread somewhere, said, I want us to think about how we put certain topics. And they gave the example of master and slave. And this was in relation to GitHub, right?
Yeah.
And, you know, even in security, we have a lot of these, the language that is, I'll call it legacy language that will attribute negative characteristics to the color black. You know, so we have a black hat and the white hats and the gray hats and And so I think a lot about this and I think about from a technology perspective, people coming up through the industry and what does this language do to your psyche? You know, because I remember the first time somebody said master slave and they were referring, I think it was a database or something.
Right.
Right. And I remember being taken aback and I was like, wait, what? And then all of a sudden it just became so commonplace that I started using it.
Oh, wow. Yeah.
Right. So this is something that it will take a long time to fix, but just being conscious of it.
Yeah.
Sometimes even the words that we use in an industry can have a negative impact on people who are hearing them for the first time and might be taking them out of context. We should be thinking about how to make changes there.
Yeah, like blacklists, whitelists, right? For example.
Yeah.
Allow and disallow. Yeah. Yeah, that's right. I think just having more empathy, right? In just what we're doing.
Exactly.
Well, Betsy, thank you so much for your time. This has been quite illuminating and I'm so happy to get your story and share your story with the world. So thank you for coming.
No, thank you. This was a lot of fun. And thank you for inviting me. And I hope that this will be helpful and useful to folks who are looking to get into the industry.
Oh, yeah, it definitely will be. So thank you so much. Yeah, this will be great.
Thanks.
All right.
Thanks.
Hey, thanks for listening. So I built a lot of things and I'm building something new. I'm working on a new community. I want to bring everyone together with all the things that I've done into just one space. So I'm really excited about it and would love to stay in touch and get some early adopters or feedback. So check out the link below in the show notes and send me a hello. And that's about it. I hope you're having a wonderful day. Thanks. Talk to you soon. Thank you.


