Latest / The Team House / NSA "Red Team" Hacker | Jeff Man | Ep. 269
Transcript
- Hey, guys, it's Jack. I just wanted to talk to you today about a way that you can help support the podcast. If you're not already, we would really appreciate it if you guys went and reviewed us on Apple or Spotify. Those reviews really help people find the podcast and help it get recognized, and you know, if you've been enjoying the show, we really appreciate your support. Another thing that you can do to support the channel is to become a Patreon member. So we have Patreon memberships that started just five dollars a month, and when you sign up, you get access to all of our episodes add free. That's the big bonus for that. I mean, we also do some Patreon bonus episodes for our subscribers, but this is the biggest and best way that you can support the Teamhouse channel and podcast if you'd like to, and we really appreciate that. So go and check us out at patreon dot com. Slash the Teamhouse, Special Operations, cobert Os SP and I The Team House with Your Hopes, Jack Murphy and David Bark. Hey, everybody, Welcome to the Team House Episode two sixty nine. I'm Dave Park co host Jack Murphy and behind the Wheels of Steel d Tonight, we'd love to you know, we welcome our guest Jeff Mann NSA for ten years twenty eight years in the crypto and hacking community outside of the NSA, So Jeff, thank you very much from coming out from the shadows and sharing your time with us. Hey, happy to join you here this evening, looking forward to having a fun conversation, a little stroll down memory lane as it were. Hey, I just want to hit everyone up before we get started and let you know about our Patreon. You find the link down the description. If you guys sign up, you get access to all these episodes ad free. We really appreciate you guys supporting the channel, so if you can please go take a look at it again. The link is down the description. All right, and Jeff, on to you. One of the things we like to ask our guests is what's your origin story? Like, how did you grow up and what led you into the crypto world, the cryptography world. Well, it's a great question, and ironically on the podcast that I'm a co host on Paul Security Weekly, we often start with the interviews with the same kind of how'd you get your start question, And for many years if somebody asked me how'd you get your start, I'd say, well, you know, I sort of cut my teeth. I got started at NSA. But I realized a couple of years ago that that doesn't really tell the story. The real story is how did I get to NSA in the first place? And I'll try to be succinct. I grew up in a family of pretty smart people. My dad was a physicist. He actually, in the nineteen fifties came to the Washington, DC area, went to work for the Naval Research Laboratory around the time that they were experimenting with hydrogen bombs hydrogen devices. I guess the first one was not technically a bomb. He used to tell stories about how he was on a ship in the South Pacific and he got to watch the detonation of the first hydrogen device obliterating a little atoll called Anniwetok. So my dad being a physicist and me being like many people having daddy issues, I grew up. I was like, I'm not going to be a physicist. Tried to avoid physics, and I did. I'm the youngest of four boys. We all liked to do puzzles. We were all sort of analytical problems solving, and I really grew up doing puzzles, Crossford puzzles, crypto quizzes. Back when we used to have newspapers and comics pages, there always be like a little Caesar Cipher type of cryptogram that you had to solve, usually like a famous quote or something like that. Yeah, I went to college, didn't know what I want to do. I graduated with a business degree because it was the easiest major I could find that required the least amount of work, the least amount of term tapers, and I didn't have to take physics. My mom at the time had gone back to work and she was working for a different naval institution called Naval Surface Weapon Center at the time, and she actually got me a summer intern job before my senior year of college, working ironically for a physicist, only this guy was doing anti submarine warfare research. My first week on the job, my first day on the job, he asked me, what do you know about anti submarine warfare? Of course I didn't know anything about it, and he's like, well, I could explain it to you, but you know, there's a book came out recently, it explains it about as anything as good as anything does. So he handed me a copy of The Hunt for Red October. So I thought this is really cool. My first week on the job and I get to sit and read a book. So summer intern job, graduated, looking for you know, what do I want to do with a business degree? I was putting in applications to a lot of different places. My mom, who worked in human resources or personnel as they called it back in the day, she had a friend whose daughter had gotten a job at this place called the National Security Agency, and being born and raised in Maryland, I had never heard of it because it used to be very clandestine and nobody knew it existed. Nobody was supposed to know it existed. There were no signs on the highway or anything like that. But I filled out a standard government application, mailed it in, got a response from them, and went to Fort Meade for a couple days of aptitude and skills testing, psych exam, polygraph and all sorts of different prodding and poking. But most of it was just taking these various skill level exams, aptitude tests, and long story short is I scored really well on the tests. And so they offered me a job. What I didn't know was they had just hired me when I first went to work for NSA. And this is back in nineteen eighty four, I'm sorry, nineteen eighty six, eighty four was at George Orwell Book. I was granted a secret clearance, but I was going through the background investigation to get a top secret clearance. Wait a couple months. While I was waiting, I essentially went on a bunch of job interviews, and I ended up in what at the time was the defensive side of the house, which we called at the time communications security, soon to be renamed Information Security later on to be renamed Information Assurants. Now sort of dissolved and you have US Cyber Command. But I'm getting ahead of myself. So I went to work for the manual cryptosystems branch, and they were looking for someone to do cryptographic analysis of manual cryptosystems that they had produced and were fielded by, primarily the military. So I went to work for him. I had somebody that was there on assignment from the operation side, a real crypt analyst. He sort of took me under my wing and became my mentor and he was actually the one that advised, yeah, this is a pretty good job, you should take this. So one of my first assignments was actually my customer was you Special Forces. So there's a little connection there, and I can tell that story in a minute. But the day I knew that I was in the right place and I had found the right place to be was you know I'd mentioned growing up, my whole family liked to do puzzles, and when we would go to vacation at the beach in the summer, we'd buy a single copy of a Dell crossword puzzle magazine that had all sorts of different types of puzzles in it, but they always had one or two logic problems, and we all love to do the logic problems, and there was usually like a little table that you could use to fill out and kind of help you solve all the clues. And basically the logic problems were like maybe eight or ten statements about a bunch of different things, and you had to try to just based on a couple of clues, connect the dots. And you know, maybe it was there's five different students taking five different classes, what's their favorite subject from five different teachers in five different classrooms, and they'd give you just very sparse types of clues like Sally loves biology and it's next to the red room, and statements like that. You put it together and try to figure out whose class you know, who's the teacher, who's the student, what's the subject? That type of thing. My one day at lunch, you know, so that was something I grew up on. One day at lunch, I'm talking to my mentor and he's working on something and asked him what he's working on. He says, Oh, I'm writing a logic problem. Like, oh, I love logic problem says yeah, I write logic problems as a side job for Dell Cross. So it was like, you know, the planets were in alignment. I knew I was in the right place. So my start at NSA was really in cryptology and I was doing analysis of you know, systems and really just signing systems. My very first assignment was to come up with a replacement a new memory cryptosystem for special forces. When they were deployed. They had at the time one time pads, paper pads with the key, the random key written out on it that they would use to manually encrypt and decrypt messages and then send them. But if they had to you know, exit someplace really really quickly, or they're on their run and they had to drop all their paper, they still wanted to have a way to communicate securely, so they needed to have a way of doing a memory cryptosystem. So that was my first assignment was to come up with a new memory cryptosystem for them. In doing that, I had just been through, you know, the five months of waiting to get my clearance, taking all sorts of introduction to cryptography classes, history of cryptography classes. I've learned about things called cipher wheels. If you've seen a Christmas story, you know, the little orfananti to ring. And I thought, you know, there ought to be a way to take a Visionaire table, which is what special Forces used, which is the alphabet twenty six offsets and a big table which for Special Force is actually translated into try to get this on screen for you. I think it's one hundred and twenty three unique three letter groupings that they called trigraphs. They would memorize these things, the commos right when you put something through a one time pad and a trigraph it's considered impossible to decrypt right absolutely. There is no cryptographics solution for it. There's no route forcing. It's completely random based on the fact that there's only two copies of the key in the world, one on each end. As long as it's not stolen or compromised and used only once, it's unbreakable. But anyway, I was struggling to I wanted to use the same essentially algorithm used these trigraphs and use this vision air table, and I thought there ought to be a way to do it on a wheel. So I like figured it out with graph paper and drew one out, and my mentor helped me with it, and we kind of came up with the design and the first one was glued to cardboard. I took it with me the next time I went to what's that place in North Carolina called now Fort Liberty. Yeah, it used to be called for we can't say it anymore. But I turned my back to right on the board, turned around and the thing was gone. They'd stolen it from me, and I'm like, guys, where's my wheel? And they're all like looking around. So after a couple of visits and bringing multiple handmade copies. I finally said, you know, we're in the business of you know, we're INNSA, We're in the business of making cryptosystems and all sorts of crypto for you. Why don't we just make a bunch of wheels. So there was a machine shop at the time of NSA, because back in those days they were building little black boxes, engineering little black boxes that would go in different places. So I had them make a prototype of this thing that we called the Visionaire wheel, so the three letter combinations would just line up, You get your two letters and the third letter appears in the window. They loved it, so we ended up producing fifteen thousand of them and distributing them to US Special Forces. This was all the different groups. This is probably in nineteen eighty eight, I would say, and as far as I can tell, they were using it up into the early two thousands until digital crypto solutions and encryptied phones and stuff became popular. So that was my very first assignment made a wheel. And if I may shameless pitch. At Fort Meade, which is where National Security Agency is located in Maryland, there is something called the National Cryptologic Museum, And at the end of this month, and of April, a copy one of the production models of what came to be known as the whiz Wheel, or I came to learn that that's what they called it is going to be put on display at the National Cryptologic Museum. They're excited about it because, you know, they're not usually putting stuff on displays where the people responsible for it are still alive. I'm excited about it because, you know, something I did that was just a little a silly little thing as far as I was concerned, actually turned out to be very instrumental in the mission of US Special Forces for over a decade. I had the opportunity to meet someone that was a former Green Beret a couple of years ago at Defcon, a hacker conference in Vegas, and actually a friend of mine met him and found out he was a Green Beret and asked, oh, do you remember the whiz Wheel? And he said yes, and they said, would you like to meet the guy that invented it? So I met the guy and long story short, he said, you know, I think you might qualify for membership in our alumni association because you kind of made a significant contribution. So he got me a lifetime membership in the Special Forces Association. That fantastic. Yeah, and I had the opportunity. You know, COVID came along kind of blew things up, but I had the opportunity to speak at their convention last year. It was in Indianapolis, which is Chapter five hundred, like the Indy five hundred. And I asked the guys there when I was speaking, I said, you know, I've been walking around with the prototypes. I have two of them for you know, thirty some odd years. I'd never seen a production model of the whiz Wheel before, and I put out an appeal if anybody was willing to donate them. You know, I was trying to get a couple, one of which was to be put in the National Cryptologic Museum. That was the goal. Anyway, they came up with two. One has been donated, will be put on display. This is another one. This is a production of the whiz Wheel, and this one is designated Uh. If we ever get a contact for the Special Operations Museum that's down in North Carolina at Fort Liberty, that's where we want to put the other one, just as a little piece of history. That's amazing. It's all pause for a minute. That's how I got my start just solving puzzles, got into crypto designed something, came up with a little quick fix that was really just an aid for me, and it ended up being something that was, you know, pretty critical to the mission, many missions that I don't even know about, of many Special Forces teams before we get deeper into it. Since you're the first, I think you're the first guest we've had on from NSA. We've done all kinds of different federal agencies. Could you explain to you know, our audience a little bit about what the National Security Agency is, what their mandate is, their job, why they came about. Sure, I mean I'm not a historian. I can give you a little bit of the history. I've probably forgotten more than I know about it at this point. NSA, I believe was started in the late forties. It was sort of after World War Two. You know, organizations that were doing code breaking and things like that during World War Two kind of got reorganized and they came up with this idea for the National Security Agency. I want to say forty eight or forty nine was when it was conventional. It's like the National Information Agency or something. First wasn't it. Yeah, you probably know more, and you can google quicker while I'm talking sure to get the exact story. It'll come back later on in my story, but I'll share it now. You know the charter. The mission of NSAY is I always used to describe it to people, the operations, what we called operations is basically to be the big ear of the country responsible for primarily monitoring and intercepting signals anything that was going out over the airwaves, which back in those days was mostly radio, a little bit of you know, eventually television, you know, maybe some telephones, but primarily radio waves the whole spectrum of sound. An ESSAYS mission was to listen to everything and try to intercept whatever they could from other countries, adversarial countries you know, nation states is what we call them these days, and you know, just keep tabs on everything. So at one level was a big collections agency. It would collect a lot of information and there'd be people that would try to break codes and ciphers when those were in play. Others would translate foreign languages that they intercepted, and there would be other people that would read it and try to you know, extracts useful information that gets put together on daily reports that gets sent to the White House and the Pentagon and other places. Anybody that you know is a customer intercept collections and communications that are collected. At a broad level, that's what the mission has always been with some rules that were put in place in the early seventies after Watergate and Watergate investigations. Senate subcommittee hearings that happened after Watergate, one of which was a Senate subcommittee that was chaired by Senator Frank Church and their output was called the Church Proceedings, and they published several volumes of material, But in essence, what they discovered as a result of the Watergate investigations, the Watergate breaking from the early seventies was that the three letter agencies like NSA, FBI, the CIA had a lot of power and a lot of capabilities at their hands, with not a whole lot of any kind of oversight or rules dictating how they would operate rules of engagement as it were. So one of the outcomes of that was what I came to learn when I went to work for NSA is the NSA Charter, which is still to this day a classified document, but basically what it says is that NSA can only do what NSA does to other countries foreign nationals, and specifically, NSA cannot do what it does to US citizens. Now fast forward to nine to eleven in the Patriot Act, the rules kind of changed a little bit, but I mean that's the charter that NSA was built on. So, but you guys are also in charge of like maintaining America's communications security as far as the US government, right, Well, yeah, I was just warming up to that, you know, Like when I went to work for n Essay, I was working on what we would have called the defensive side information security, communications security, and it was you know, probably classified at maybe ten or fifteen or twenty percent of the mission of the personnel and the resources of NSA. So even when I was there at the time, there were people there that were had been there for a while, working the mission for a while, and everybody sort of had a chip on their shoulder. Everybody was considered INFOSEC, as we called it, sort of the bastard stepchild. Because operations got all the headlines, operation got all the budget, operations got all the glory, and INFOSEC, which was the mission of providing secure communications and crypto to all of the US whether it's the military or any level of government where they needed to have, you know, secure communications. That was NSA's purview, that was NSA's responsibility the infosex side. So I came into an organization that kind of had an inferiority complex, always always did and probably always will. Of course it doesn't exist anymore, but it was. There was always this conflict between operations. What everybody knows NSA, that they know what NSA is, what they're doing, and then us doing the really important stuff that you don't get any credit for, like making sure that people can't steal any of our communications. So a lot of cryptographers, a lot of mathematicians coming up with the algorithms and the and the machines, the little black boxes that would secure the communications for you know, the military primarily, any level of government, inter departmental communications, you know, embassies abroad and things like that. And you you went in, you said you went in in around eighty six, Is that correct? Correct? So the Cold War was still a very real thing at that point in time. Why, yes, yes, it was, which is one of the main reasons why I was hired. I was hired at a time when NSA was hiring one hundred people a week, and they'd been doing that for a couple of years because they'd gone through a lean time in the seventies where they really didn't hire that many. People like the guy that was my mentor had been hired in the early seventies, and then they had just had a handful of hires from like the early seventies to the early eighties, and they really hired a bunch of people. This is where I get a chip on my shoulder. We didn't call it STEM back then. They called it critical skills. But they were mostly looking for mathematicians, computer scientists, and engineers, and if you had a degree in any of those fields, you would get a job offer, and you were paid on an accelerated pay scial, so you got paid extra. I think the engineers made the most, but don't quote me on that. Anywhere from ten fifteen to twenty or twenty five percent more than what I was making as just a peon regular employee. But you know, they hired me because I scored well on the aptitude tests, the skills test, and so I was not a critical skill and those hundred people around me that were hired the same week I was. They were first in line for promotions, they were first in line for training opportunities, first in line for diversity tours going to other organizations. Because the game at the time was, if you wanted to be promoted up past a certain level, you had to have what was called a professionalization degree. And the professionalization degree would be similar to searchs that we know of in the cybersecurity field these days. And to get that. To get that professionalization, you had to have a certain amount of work experience, a certain amount of diversity of work experience, working in different places. You had to have continuing education, and various depending on what field you were choosing, in various other things. You know, if you wanted to go into the computers, you have to write a computer program at some point, and so on and so forth. So I, being just a regular employee, uh was, you know, not getting the opportunity to get the diversity tours. And I tried to get into an intern program and I wasn't qualified for it, not because I wasn't a critical skill, but because I had a horrible GPA in college. I won't say what it is on air, because people would be shocked. But you know, my mentor did a good job of kind of nurturing and talking to friends of his like on the operation side of the house, and getting me some diversity tours on my own because he knew I was going to need it. But yeah, they they hired a bunch of people. They would go off to get a graduate degree and the government would pay for it. They called it the twenty twenty program. So they'd worked twenty hours, go to school for twenty hours, and then they had to give back government time to offset the time that they went to school. But what they failed to figure out for many years was the clock was running as while they were in school in their retirements. So you could literally like go go to grad school, get a graduate degree completely paid for by the government, and after about three months you could quit and go out to the private sector and get paid more. And that's what a lot of people did. So they were kind of growing by attrition. And because I didn't qualify for the twenty twenty program, initially I didn't get to go to that, I didn't get to do the intern programs. I just sat in this little office and designed a wheel that was used by special forces for twelve years and I'm told saved lives. I was also there at this sort of the beginning of the computer age, you know, IBM PCs were kind of a thing. I think, you know, my first office I had a standalone IBM PC. It wasn't it wasn't networked yet, it didn't have windows on it. It was just doss. In fact, I think my first one didn't even have a hard drive. But one of my my one of my early assignments, I can't say it was my second assignment, but one of one of my early assignments in this office was I was approached by another customer, another military branch, and they were they were responsible for communicating with one time pads with people that, shall we say, had been recruited in certain places in Eastern Europe. And the one time pads that they were using in the field were really tiny and they could hide in the heel of your shoe type of thing, and they were printed on rice papers so that when you used it you could destroy it by eating it. But the the caseworkers, the handlers were in skiffs controlled spaces offices on the you know, on the good side of the world, and their version of the one time pad was sort of like a legal pad. But they came to us and they said, you know, it takes us hours and hours to decrypt and encrypt these messages because they're getting situation reports from these people. And they said, there's this PC sitting on our desk, is there any way we could use that? And me, being young and naives, like, yeah, I don't see why not. Of course I didn't know it at the time, but I was working for an engineering organization whose mantra was there's no such thing as software, there's only hardware. All they did was build little black boxes. So I took up the project of coming up with a design for writing a computer program that could run on the IBM PC and taking the one time pad key and instead of printing it on paper, putting it on a floppy disc, which I forgot to grab. So you'll have look at the save icon on you on your word dying, and that's what a floppy disc looks like. And I had to go through an engineering process, a design view process called d FSRS Functional Security Requirement Specification. It was specifications to build secure hardware. And I was building a software program so I kind of had to fudge my way through it. I had to go through a review process with all the executive management of INFOSEC. INFOSEC was oregonaute. It was a directorate, and inside the directorate were various groups, and every group had offices and divisions and so on and so forth. But all the group chiefs, and there was like five or six of them, got together and that was the Board of Directors as it were, and I had to present the ideas to them, and they said, yeah, go ahead and do it. And I came back with the design and had to go through its own security review, which produced issues that had to be addressed. And I went through that process and eventually went back and pitched it to them and said, Okay, I've met all the security requirements, met all the objections, were ready to go. It's ready to field. And the director, the chairman of the board, don't know what his exact title was at this point, he said, okay, we'll let you do this, and literally he said, don't do this again. To my knowledge, it was the first software based system that NSA ever produced, and it was simply a computer program that would automate the process of doing a manual encryption and decryption with a one time pad. But I actually ran into somebody about ten years ago at a conference that remembered using it. We called it Centaur because it was a half paper and it was half electronic, So Centaur. Every system we produced had to have a cool mythological name attached to it, so we came up with Centaur semi automated one time pad. Can't show it to you because it was software, so just to like it, correct me if I'm wrong. Trying to paint the picture. Here, the person on the end user in good guy land is taking like an Oregon trail flyop, putting it into the computer and then typing in the encrypted message he had received, and the computer would spit out the decrypted correct, yep, that's pretty cool. And conversely, if he wanted to send a message, he's typing in a message hitting the button to encrypt it. And the trick was. One of the secrets of a one time pad is you use one page at a time, as much of it as you need, and then you destroy it. So we had to come up with a way of securely deleting a page of key at a time off the floppy disk, and part of that was coming up with a secure deletion or a secure overwrite routine. That was a requirement, and so I went searching and asking various offices. You know, can you can you show me one? Can you give me the specs for one? And it had never been done before, so we had to come up you know, it was a requirement, but we had to come up with what would this look like? And so we had to come up with a routine for doing an overwrite of the one time had key that was on a floppy disc, doing it in enough so you know, other really smart people at similar agencies couldn't figure out how to wait to read the read the data off the off the a floppy drive you used to be like a flimsy piece of plastic where stuff was printed on it. You knows, bits and bytes in various sectors, kind of like a vinyl album, only smaller and much more compact. And you know, things that get deleted off of memory space on floppy disk and hard lives traditionally, at least in those days, didn't really get deleted. You would just you would move the needle to a different part of the record and start writing new information there and the to where your information was, which was sort of kept in a master list on the drive or on the floppy disc. That was a race, so you didn't have the location anymore. But nothing was done to remove the data off the drive itself. Eventually it would come around and get overwritten. So we had to figure out how do we zone in on exactly where it is and delete the right amount of keys so that it can be done. So there was some engineering as it were, or software design that had to be done, and people weren't happy about it, but they let us do it. You know, in the late eighties or around that time, how were you keeping up with what was going on in the computer industry because it was moving fast. Like I remember like an eighty eight hearing about like the first one gig hard drive and thinking, what would anybody ever do with a gig ab a hard drive? That's insane? Hey, I had the same thought when I got my ten megabyte hard drive on my IBM PC. Yeah, who wouldever fill that up? And now I think I have more storage space on my smartphone than the supercomputer that I used to use. Yeah, in the early days of NSA, So yeah, I mean, there was try to be a politically polite answer to that question. On the operations side, all you've had all you have to do is figure out how to intercept stuff. And as communications got more advanced in terms of the cryptography, you you and other sister organizations perhaps come up with other ways of capturing the data, perhaps maybe before or after it's been encrypted or decrypted, you know, and that's the land of espionage and so on and so forth. On the infosex side, it was actually really a struggle, and I saw it at the very beginning, and it came to a head, you know, later on in my career in the early nineties, where technology was catching up with infosec, which was, you know, responsible for taking three to five years to design a little black box and we'll get it to you when it's ready, and we're responsible for providing you know, all this year communications probably the first skipping forward a little bit, but the first real test of that for the government in general, but for Nissey in particular, was when a program came out called Pretty Good Privacy, which you know, don't quote me on what year it came out, probably late eighties, early nineties, and it was an encryption program, and it was written with public algorithms, not NSA designed algorithms, and it was based on what we call public key cryptography, which is where you have a pair of keys, one that does the encryption and one that does the decryption, and everybody uses it if you're online at all, every day, multiple times a day. But the idea is you have a public key that is used to encrypt the data and that can be sent anywhere. It's not secret, and the only way you decrypt a message that's been in with that key is if you hold the secret key, and you hold that close. That's the private key, and it's a one way relationship like that. So you have to do a key exchange. If I want to communicate with you, I give you my public key, You give me your public key. We do something to verify we're really talking to each other, and then we're often running we can send messages to each other. Well, so fast forward a little bit. You know, I left the Manual Cryptosystem's office. I was there for about three years and then I did finally get into an intern program. There's not much to this story, it'll go quick. I went over to the operations side of the house. I did happen to be there during Desert Shield Desert Storm, so I got my Certificate of the Appreciation for participating in Desert Shield Desert Storm. I was as an intern, so I was doing six month tours in various office. My last tour of the interim program was back on INFOSEX side in what was called fielded systems evaluations. So we're back into the I'm back on INFRASEC. It's the early nineties. There was a time when one of our clients, and this was probably I would guess ninety three or ninety four, one of our clients, one of the military branches, came to NSA and said, why are we spending multimillions of dollars on a secure communications system with you guys, why can't we just use PGP? And that was really a slap in the face to the power structure of at least the INFOSEX side of things. And there was literally an all hands on deck call put out for everybody in infosec to stop what you're doing. Everybody work on an attack against PGP. And there was a couple guys in an office nearby that actually did come up with an attack against it, and they were paraded around as heroes. They got huge cash awards, They were taken down to the Pentagon, the White House, I mean, the red carpet was rolled out for these guys. Months later, you know, when all the dust settled down. You know, everybody's got a short attention span. They did a lunch and learn in our lab to just tell us peons that worked with them about the attack that they'd come up with PGP. And what they essentially had done was figured out a way to send a document, let's say, a word document, only it wasn't word it was but some predecessor, and they found some unused bit space in the document that they were able to insert a virus, as it were. And you know, if they sent this document to somebody and could trick them into opening the document, it would execute the code that would essentially steal the key rings, the secret key rings, and attach it to an email back to whoever had sent the email. That might sound familiar to you guys, if you keep up with cybersecurity scheme today, it sounds a little bit like a phishing attack. Yeah, only we don't you know, we don't click on attachments anymore. We click on links. But I remember sitting there and you know, hearing them describe this, and then they got to the point where they're asking, you know, does anybody have any questions? And I raised my hand, I said, wouldn't this work against our stuff too? And they kind of looked at each other and they're like, well, yeah, I said, well, so what's the big deal? Said, well, our mission was to come up with an attack against PGP, and that's what we did. I'm like, okay, if that's what if that's how you sleep at night. But yeah, I mean well, and which is very and I'm not it was funny then at the time, and it's kind of a funny story now. But I mean, they did make a difference. They did come up with an attack. But as is true most often, and I've been in this business, you know, forty some years, when you're attacking crypto, very rarely are you going after the algorithm itself. You're you're going after the implementation and either the implementation of the cryptography itself or what we call the key management or the key distribution. So they didn't essentially break the algorithm, they just stole the key. Right When has that ever happened before in the in the history of the world, right, Jeff, can I can I back you up real quick? I just want to ask because you were, you know, the Soviet Union was a real threat when you joined the NSSA, and then eighty nine the Wall fell and the Soviet you know, it was no longer. Did the NSA it all go through any kind of identity crisis? Were there issues where like who's our enemy now? Or did you guys just kind of have a mission and drive forward there? I don't know if anybody in power would admit to it, but absolutely there was issues because once the Great Satan fell, that was Reagan's term for President Reagan's the Evil Empire. Once they fell, yeah, for the first time in a long time, NSA had to worry about, uh, you know, budget requisition. They had to go before Congress and justify what they were doing. And I'm not a conspiracy theorist, but you know, Desert Shield, Desert Storm happened shortly after the Wall fell, and you know, terrorism became kind of the thing that kept things alive. But that wasn't really a clear, a clear and present danger. Vote. In my Tom Clancy books, it wasn't something you could put your finger on. I mean, you know, I remember watching videos about terrorists when I was waiting for my top secret clearance to come through, and and you know, classified briefings at the time about you know, what did the terrorists do back in the seventies and eighties. They'd hijacked planes, They'd blow them up, you know that, you know, they that was the thing back then. You know, there there was you know, one plane in particular that you know, nobody knew it, but there was people on it from NSA and c i A, and there was suspicions of whether people knew they were talking about. I can neither confirm or deny that. It's been a long time, so it's probably declassified at this point. There was the one plane where they landed somewhere and they they killed a passenger and shoved them out the wind. The pilots went down. Yeah, and it was it was a I think was a Navy enlisted person and they the reason they tagged him or pulled him out was because he was in uniform. Because what I remember hearing at the time, you know, the briefing I got, the video I watched about that was there was a flight attendant that had been asked to collect the passports of all the passengers, and for whatever reason, US citizens get a blue passport, but government employees get a red passport, and so she was able as she was collecting the passports to somehow hide the fact that she was collecting red passports. I mean, when I was at NSA, I was issued or read it's more like a burgundy passport. That's your official passport to use on international travel, and you're only allowed to use that password. But then I was pulled aside and said take both, and I did. And you know, for the official get through customs, the red one comes out. Everywhere else it was the blue password. I'm just Joe's citizen. Much because of that experience of that plane beaming hijack. So, yes, there was an identity crisis. There was a justification for budgets that had never been realized before, and computers were becoming much more a thing. I mean, we sort of leap frogged over the whole machine age into the digital age, and NSA was largely unequipped for that. Uh and slow to slow to respond, you know, think, you know, probably too soon, but you know think a large ship that's, you know, pointed towards the pylon of a bridge, and how hard is it to steer that and turn that thing right. I'm five miles away from that particular what used to be that particular bridge, So they were very slow there. There was also a certain amount of attitude, I would say, in in sort of the old guard, where like, you know, people, can you know it was? Is it Henry Ford? You can have whatever color car you want as long as it's black. I mean, they sort of had a monopoly on crypto, and so they weren't very quick to change. They did start farming things out to contractors and third parties. The classified telephone that was popular at the time that I was there called a Secure Telephone Unit STU, and they were up to the STEW three, the third version, which looked like an old fashioned office desktop phone, and there was three contractors that were allowed to build it. It was RCA, GE, and Motorole. I believe in the three models. If you're old enough to remember those and have worked for the government. So early nineties, I'm back in this fielded System's evaluation office, and that's where I started doing penetration testing. Is what we called it then, but trying to break into computers and network systems. We were assigned to break into military facilities throughout the world, and at some point we decided, why don't we just call it penetration testing, because that's what the world's calling it. Let's become hackers. So that was the early nineties, the NSA trying to respond to the changing world, they reorganized and formed what they called the Systems and Network Attack Center. It was the vision was that it was going to be a center of excellence and they have all the really smart people in NSA has lots of really smart people, and they were going to be experts on everything related to computers and networks. And of course we'd been doing this for a couple of years at that point, the small team of people and we were we had realized because of being involved in something that's interconnected, we realized very quickly there's a whole lot of people in the world that are focused on this problem. I don't care who you are. You have small subset of ten twenty one hundred, two hundred people, there's no way to compete against the whole world, right for that kind of brain power and distributed thinking, let's say. But they went about doing the reorganization, and that's when the office that I was in got pulled into it and we were sort of formally given the task, the small group of people that I worked with of just doing. We called it vulnerability and threat assessment, but for lack of a better term, we said, we're hackers and we're learning how to do pen tests. So that was we were formed officially, I guess ninety three ninety four at least in terms of this new organization. Now we moved to it. I'm sorry, I just want to I'm curious because you, coming from cryptology, had computers been a hobby? You know? Had you been learning see or like C plus plus like I don't I don't know what language or languages were prevalent at that time, but but how were you personally and then as an organization? How were you managed? How are you catching up with these teenage kids who had nothing better to do than to figure out how to you know, break in a shit? Well? I mean I graduated from high school in nineteen eighty and I remember taking a computer math class, so it was late seventies, but it was a you know, a very rudimentary type of PC. I think I was programming in basic. It was kind of cool. We wrote our programs to punch tape. It was it was even before the before the era of floppy discs, so you know, I'd have two or three or four feet long of punch tape that I would have to feed into a machine to read my program. So, you know, I was kind of interested in it. I had an older brother, one of my older brothers, uh, you know, sort of the brain of the family. He was he got he was into physics and engineering, and he was always buying the new toy of the month. Uh so he you know, he built a computer, uh you know, build it from scratch, kind of like you build you know, the old Ham radios. Of course, he did that when he was a kid, but at some point he built his own computer, very rudimentary and then you know what was popular at the time, the Apple twoey or Macintosh or something like that. He was always getting computers. He was the first one to have the first video game, Pong, and he was the first one to get a Nintendo and an Atari. You know, I kind of grew up playing video games at the arcade everybody remember that, you know, put a quarter in a machine and play the game and and keep putting the quarters in. So I was into it because was new and it was kind of fun and different. But I wasn't like how does this work? And digging into the innards of it. But at NSA, you know, when I was in the interim program, I had to write it. One of the assignments was to work for a programming office and I had to write a computer program. That was one of my assignments. And at the time, NSA was converting from their own mainframe supercomputers that they had their own custom operating system on it and their own primary programming language that all their number crunching, cryptanalytic, calculating, statistical counting types of programs had been written on. They were migrating over to what at the time was fairly common Unix workstations primary Sun microsystems. Later, you know, Sun os later be called Selearis. So the IBM PC left and in came a Sun workstation, the old pizza boxes, Spark five tens whatever they called them. So I had to rewrite a program that had been written in a proprietary language at NSA. In C and of course I got it to compile and then got it to hang the first time I ran it because it worked, but it didn't optimize for the number crunching type of thing it needed to do, so you know, I did that. It was kind of cool, but I wasn't really into it into it, but the idea of breaking into things that was kind of cool. The idea of going someplace where you weren't supposed to be learning a hidden trick or a hidden feature. There weren't many exploits in those days. It was mostly features of the operating system undocumented or undocumented, or just learning the tricks of how to fool the computer or trick the computer into giving you stuff. And of course a lot of stuff was there, and it wasn't that hard to do, and you know, other people had figured out a lot of the ways to do stuff. So you know, the terminology in those days was script kitty, So starting out I was much more of a script kitty, just doing the stuff that other people had figured out, but trying it on our classified networks, even though it was, you know, something that was discovered out in the real world. But because I had a cryptanalytic background, one of the things that I enjoyed doing was password cracking. And you know, of course I didn't write the programs. I was using the programs that were available at the time, but learning how to tweak them and fine tune them. Password guessing was a thing back then. I was actually pretty decent at guessing passwords. Nobody does that anymore these days. There was a lot of our a lot of our customers when we were doing these field and systems evaluations, we were going to military basis throughout the world, and they always had like some you know, real whipper snapper teenager, but he was also you know, an E four and E five now, and he was, you know, because he knew computers. He was responsible for computers. So he came up with an idea of coming up with a random password generator. Uh. And so they had all, you know, they knew passwords security was a thing back then, so they wanted to come up with ways of defeating the password cracking tools or just making passwords less prone to being guessed. And they inevitably were horrible because you know, from a cryptanalytics, statistical, brute forcing perspective, they almost inevitably fell. I mean, I remember one guy, I want to say he was at a base, doesn't matter where he was, but you know, he thought he had this program that was really cool and it was producing really random looking passwords and we cracked one hundred percent of them in minutes. You know, it just was that bad. So that's where I kind of like applied the trypt analytics stuff that i'd learned to some to some aspect of it. And we didn't call it cybersecurity at the time. We actually called it internet security. But that was something I could kind of focus on as sort of a niche areas like, oh yeah, I'll focus on like password cracking and how to come up with strong passwords or random passwords and any of any of the few types of crypt analytics things that were associated with operating systems at the time. That was sort of my focus. The other focus I had, I guess was I worked with people both while I was at NSA and then even into the private sector days years after that would love to just break into a system, get root it was all root because it was all Unix back then, and say they were done. And I was more like, well, we've just broken onto a computer or a server. Why don't we look at what's on it and see what's there, what kind of information is there? They were all about the hunt and let's conquer another box, let's root another box. I was more about the analytical, Well, what kind of information is here and what can we learn about our our target or our customers, or what is sensitive here that might give us more of a clue of where to look next, or you know, if we found the Crown jewels or you know, just whatever it was, but just looking at stuff. So I tended to do more of a analytical deep dive, let's see what we've got, rather than just keep knocking over boxes after boxes after boxes and saying we're done right, moving on. So how did that develop for you? Because while all these other people are trying to like get root now, you want to get into the system. You want to go through the various like you know, file systems and everything like that, right, you know, and move throughout this system. Like what does that look like for you compared to what everybody else was focused on? So back in those days, the sort of the methodology, which ironically is based mostly off a film that came out in the early nineties called sneakers. Robert Redford and Ben Kingsley were the stars, and that was sort of the first movie that showed what people would more commonly refer to as a red team exercise these days, because you know, a combination of computer hacking but maybe physical penetration testing. The methodology was simply back in those days, you have a target, you have a company, an organization. Everybody had their own IP routable IP addresses. There was no masking back in those days, or no private addressing. Every thing with the Internet reachable because everything was connected. So you'd find out what the target was, whether it was a Class C address or a series of Class C addresses, which is two hundred and fifty five potential addresses, and then you do a probe of each IP address to some sort of rudimentary scan to see what's alive, what's answering, and so once you found live targets, you do a port scan, which is basically, okay, what's this machine talking on? You know, in TCPIP there's sixty five thousand, five hundred and thirty five potential channels that you can talk on, and there's some commonly associated reserved ports that are associated with specific protocols, specific services start with there and most of the protocols communication protocols back then or clear text. There wasn't a lot of encryption going on, so you would find what they were talking on and then you know, that's usually when you could connect to a system, maybe steal a password, maybe guess a password, maybe force one of the programs that was listening to hiccup and give you accessors. There's many different methods of doing it, but the goal then was to get access and it didn't have to be root, it could just be any user account. And then once you had that foothold, that toe in the door, then you try to elevate your privileges to root. And once you were on the system. There was any number of ways of doing that, including reading the password file, which was world readable. Anybody could look at what the password hashes were that I'm not using the word correctly, the encrypted passwords, they're hashed passwords. You could copy that and run it into your computer pracking program, which conveniently was called crack. So elevating privilege, I mean, that was sort of the modus operandi. The first thing to do is get the root, because once you're at Root, you have access to everything, any file system, any fold or any anything that was locked down and protected. Root had access to Because Root was what we called the God account. It could go anywhere, it could do anything, which is why we used to say to our clients, if we've got Root, we're done. But they would very rarely understand that, comprehend that, and take it to heart, which is why it was. It became beneficial to say, Okay, you're not getting it that we have Root, but would you understand it if I said, we're looking at your financials for the previous quarter, and we can and we can see all of it. Or we can look at the payroll and tell everybody you know what they're being paid and who got what bonus and the people sitting next to each other, one person's getting paid fifteen percent more and he's a guy and she's a woman, and we can blow things up. Or you know, research data, or we know where the money is. You know, there's there's any number of things that tends to be something that you know. I have no idea what you're talking about getting Root, but you can do this right. I mean, when I was and I'm blurring the lines a little between my NSA days and my private sector days. But when we first started out doing this at NSA and people started and we started calling it pen testing, and we started being asked not by just you know, our military customers, but like offices within NSA and other classified networks, you know, within the community. We started kind of having to come up with processes and kind of formalize the methodology because we had to get permission to do it. You know, I mentioned early on in the interview the church proceedings in the NSA charter. That became an issue at least early on, because you know, even though we were white hat hackers were the good guys trying to break in. Because we're NSA, we technically weren't allowed to break into computers and networks that were US right owned and operated. But you know, as long as it was in the classified world, it wasn't really that much of an issue. But we did have to start talking to our general counsel, and for whatever reason, I volunteered to do that. You know, I was a business major, so finally I was like, oh, we need organization, we need structure. I can do that. My friends that I worked with, they were much more into the gears and you know, the weeds of the technology and like business processes. I got that I can do that, so I started talking to the lawyers. I tell a story that well to the level set everything that we did in terms of our techniques for breaking into computers and networks. When we were working within the classified realm, everything we did, by rule had to be classified at the level of our target. So naturally, if we were working on top secret systems, everything that we did was classified top secret. In order to get authorization to do top secret stuff against top secret targets, you had to go through bureaucracy and red tape and get all sorts of permissions, which took a god awful amount of time. I mean, we literally would have to wait weeks to get permission to try to break into something that was even within NSA, like another organization, another office within NSA. And of course what nobody what we didn't tell the powers to be we'd already broken in, we already knew how to do it, and then we'd do the paperwork of you know, this is the way we're going to try it, this is our attack methodology, and then we'd have to go off and get permissions, which was on a typed up piece of paper that had to be signed or initialed by every level of management from our branch on up to the group level, over to the group that was the target, and down their management chain. And this is paper passing from desk to desk, secretary to secretary. It might sit on a desk for hours or days, so it would take weeks. I tell this story in a talk I've given a couple of different conferences, but usually when I'm telling this story about what was our tradecraft what do we do? I have to qualify and say technically, I can't tell you what we did because it was top secret. And then at some point I say, okay, I'll tell you one. So I had this big disclaimer banner top secret, and I say, okay. One of our primary cyber weapons that we use to get against top secret systems with something called the ping command. Let that sink in or if you don't know what a pin command, it's a system level command that comes with every Unix operating system. It's basically and it's named after a submarine sonarch. You know. It sends out a signal and waits for a response. Are you there? Yes, I'm here, and it'll ping every single address on whatever your target space. Is very rudimentary, very common part of the operating system. It's a feature. But because the lawyers looked at it and said, well, you're eliciting a response from the target, Therefore this has to be considered an active attack. Therefore it qualifies as a top secret cyber weapon. Wow, that's the logic that we were dealing with, and that's where I kind of like, Okay, we got to fix this. So I started talking to the lawyers and started teaching them about our methodologies, and their idea was, why don't you just show us what you do and we'll preapprove it, so that when you get a job request to do an attack, you can just tell us, well, we're going to do a little of this and a little of that, and a little this over here and a little of this. It will be kind of like an ala carte menu, and we already know what they are and what they do, will just preapprove it and it'll be pretty quick. I'm like, yeah, the problem is you don't know what you're doing until you're in the middle of it, right, and you know it starts with the probing. We called it recon. You know, what's out there and what's out there? What are they talking on? What you know? How are they communicating, what are they listening on? What? You know? What are the ports and channels that are open. So I went through a process. I would meet weekly with our lawyers and just sort of teach them the fundamentals of penetration testing and hacking and how do the computer networks work. And I say all this because one time I was showing the lawyer, even though he was sort of on an isolated some network that he thought was very super secret because he's dealing in all sorts of legal proceedings and investigations, and he had his folders and files and his computer that he thought was completely protected and top secret. I'm like, well, let's look at that. So we were sitting in our office, which was in a physical building that was different, probably ten miles apart. I said, let's go. Let's let's go over to your network. See here we are, here's your file system. We're on your system. Now. We had him log in and I said, let's look at your directory structure. And I'm looking through it, and you know, Unix file permissions. There's this concept of the owner, a group, membership, and then the world. And for each category there's the option of read only, read and write, or read and write and execute. Let's just go with read for now. I was looking at his folders that were supposedly top secret his eyes only. I'm like that, folders, not only you're readable, and not only the lawyer group readable, General Counsel's office readable. It's set that anybody read it. Look, I've just clicked on the folder. Here's all these files. Look, I can click on you know, this document here and open up. But he's like, oh my god, don't do that, that's all secrets off. Oh my good. So he got this really great education on how to set file permissions so he could actually lock down his folders. And you're not doing anything. You'reprely technical right now, you're just accessing his network and he has open permissions. Like you're not even technically really hacking. You're just showing him how much access a knowledgeable person would have, right Yeah. And that's a good way to sort of summarize it, you know, I mean the hackers that are out there these days, the security researchers they're trying to come up with creative ways of breaking things using a methodology that's similar to what was done back in those days. But in the early days it was much more just taking advantage of what I would call undocumented features, how can the system do? And taking advantage of knowing more about how it works than the users, because in the early days, most used didn't really know how it worked. They could barely get it to work, and they were happy if they could get it to work, and wasn't anybody telling them to do anything else. I have a question as you describe all of this, it actually reminds me a bit of you know, Richard Marsenko's Red Cell, which was testing physical security at military bases, and you guys were, of course doing that in the electronics space. I was wondering, did you guys get any sort of like pushback or political fallout from what you were doing, like people who are shocked or embarrassed and maybe even angry that you were able to penetrate their systems? Interesting segue question. Initially, know when it was mostly you know, military targets that they'd asked to do it, and then internal targets that I take that back. We did have one internal target one time that you know, supposedly that they were isolated with internal segmentation what we would call it these days, but suppostly there's a firewall or some sort of router with some sort of access control lists in place, and we were doing initial probeup probing and we had I think we had a target of either an IP address or maybe an IP range. But us being us, we just kept going. It's like, what else can we see? Where else can we go? And this particular target, which was an internal office, they did have some sort of monitoring in place and they were detecting our activity, and you know, we technically went beyond the bounds, but you know, we didn't break into anything. It was like, well the door was open, you know, everything was answering. You know, we were just we just kept going. There was nothing blocking us. We didn't subvert anything. We just this is how far we could go. But there was a point where we sort of got called to the carpet it and I guess I've been doing a lot of the work and I got called into a meeting with the customer and the poor guy. I still feel sorry for this guy. The guy that they had assigned to be like the investigator. He was a very apparently some branch of the military police, and he came in with like a stack of notebooks with printouts of all the activity that he'd seen us doing, me doing, and had it all printed out because they thought they'd caught a bad guy. He was like, oh, they're ready, they're ready to throw the book at us, and we're like, well, no, we had this request to do this thing, and we just kind of didn't know where the boundary was and we just kept going. And they're like, oh, well, thanks for letting us know. We didn't realize it was that for us. And the guy was like he didn't. He never got a chance to open it. I mean, it must have been a foot high. This might be a little sensitive, but I mean as far as like the attack services that you guys used, I mean, did you have to be inside the NSA to get to you even launch this attack, or were you guys replicating an outside attack, you know, perhaps a foreign adversary. Well, you know, our targets, at least in that case, were internal, internal and technically whatever we was doing. What we were doing was classified at the level of the target. So technically what we were doing was top secret, but it's probably a safe bet to think that we were doing a lot of the techniques that were publicly available because guess where we were learning how to do it hopefully accessible stuff. So yeah, that's how I'm going to answer that question. What was your relationship like, because like I remember, you know, in the late eighties going to my local game shop to buy D and D stuff and there was always a copy of twenty six hundred there and magazine and you know, and for people who don't know, twenty six hundred was like like the og I think, you know, hacker like little booklet, magazine, pamphlet type of booklet thing. And then the def Con started in the early nineties, so there was this there was this vibrant hacker community out there that was moving along with times from you know, Captain Crunch, you know, and Freaking and all that. How was your relationship with them, these people who were sort of breaking the law and on the cutting edge but also like pushing it right. I mean, at the time, we didn't interact with many of the people in that part of the community. I've certainly over the last ten years or so had had the privilege of meeting many of those folks, yeah, and comparing notes and so on and so forth. But I mean we were certainly learning from them. I mean we we you know, back in those days it was bulletin boards and mailing lists and you know, you know, our our best resources was the Internet and learning all the places where people were posting stuff about hacking and breaking into things. So we were certainly learning from them. And I would even say that we we felt like we were behind them. I mean when we were when we were considering ourselves to be students and learning all this stuff, I mean that they were doing it and we were just trying to pick up pick up on it and learn from them. So there was, I guess, from our perspective, a certain amount of respect. But you know, there there's a handful of people that kind of went south of the law and got caught and prosecuted. Uh. You know, I have different opinions on some of those people. There was you know, certainly uh mythology associated with it. You know, there's sort of you know, the elite, elite hackers that you know, the the uber hackers is what we call them. Back then. You know, I hope to somebody someday meet some of them. But we were kind of learning and doing stuff and figuring out stuff. We certainly had access to a lot of resources that a lot of people don't have access to. I mean, we had access to Unix source code. And this is the before the days of Linux and and the Unix source code is something that you know that the agency NSA paid you know, god knows how much money for, so you know, we were able to look at all the internals, all the function calls, all the libraries. So, I mean, we we had a fair amount of opportunity to tear things about. We had to tear things apart. We had a fair amount of resources that maybe not everybody has, but we still considered ourselves to be students and learning. You know, it's funny because, uh, you know, we'll get to why I left the NSA in a little bit hopefully, but you know, was out in the private sector for a few years doing the penetration testing and trying to get basically trying to convince companies back in those days, if you're going to play on the internet, you really need to have a firewall, You really need to have some sort of secure architecture. You need to have some sort of clue or plan as to what you're doing, So you need to put a security program in place and figure out what it is you want to protect and need to protect. And at some point I got really frustrated with, you know, being hired by clients every six months to break in and we'd break in the same way time after time, and we tell them this is really easy to fix, and they didn't seem to want to care to fix it. And at some point I'm like, Okay, I'm done pen testing because that doesn't seem to be getting the message across. And I ventured into, you know, I need to just be able to talk to companies and explain it to them and explain why they care and explain why it matters. And about the time I made that decision and is about the time that this thing called PCI came along the payment card industry and I got I got sucked into that. But it was nice at the time because there are a lot of companies that had to do PCI and it's a it's a it's a it's a private sector regulatory security standard that's of buy and for the credit card industry, so it's not a federally mandated thing, so it's a voluntary. But if you don't do it, you don't get to take credit cards if you're a retailer or any kind of business that wants to make money. So it was for me, it was beautiful because it gave me a captive audience. And I did that for a lot of years. And one of the one of the people that I worked with at NSA in our little hacking group or pen tests, went out into the private sector, became an entrepreneur, started a company, and it finally agreed, you know, we finally came to terms, and he found a way for me to come work form and when I came to work for them, which is got It's been ten years ago at this point, he said, Oh, I want you to be an evangelist. I want you to start going to the conferences and start telling stories and do some you know, you know, talk about the stuff that we did. And and so I I you know, having I mean, there wasn't much of a hacking community in terms of conferences and training and starts, you know, back in the in the When did I walk away from the early two thousands two thousand fourish, but you know, compared to twenty thirteen, twenty fourteen, twenty fifteen, where there's lots of hacker conferences all throughout the country, there's security B sides conferences, so on and so forth. So I you know, I was like, I was kind of nervous because I've kind of been away. I walked away from pen testing. I was just talking to people for you know, the better part of ten years and explaining a particular security standard, which to this day is still a decent standard, and you know, here's all the fundamental things that you should think about and do. But as I went back to the conferences and started meeting people, and over time, I've you know, one of the thoughts I had was, Oh, I'm going to meet all these smart hackers and they've had ten years to keep working and growing. And I've been going to these conferences now for ten years and I'm still waiting to meet those uber people that UH were that My perception was they were so advanced, and not to say that I'm advanced, but I think we were all in it together, and we were all at a simmer similar level, which is always learning. I mean, nobody nobody claims to have the complete understanding of all of this. Uh, there's always more to learn, and there's always more to discover, and there's always layers and layers and layers. But I've had the privilege of meeting a lot of the people that were I considered to be the pioneers and my heroes. Over the last couple of years, I've met a lot of people that were members or some of the famous uh you know, hacking groups and hacking collectives from back in the back in the day. And I've I've met a lot of people and they and I apologize if this I hope this does not come across as egotistical. But as I meet all these people that are you know, farm away from the Midwest, you know, got into phone freaking to get free long distance and then later free cable, and they just kept going and they figured out some things. Nobody's had the experiences that I've had, right you know, which you know, and for me it was just you know, the right time, in the right place type of thing. But I've never met anybody yet to this day that I'm like, I'm completely in all of an uber or two exceptions, the uber hackers. Most of them are almost as much as excited to meet me as I am to meet them. I remember, before COVID, I think the last Defcon, so it would have been in twenty nineteen. I was sitting around with some folks and one of the guys I was sitting with was a guy whose name is Weld Pond. He's a member of the Loft, which became famous back in the in the nineties for figuring producing one of the one of the first, if not the first password cracking routines that would work on Windows passwords. So it was called Loft Crack. And they were a hacker collective, a bunch of smart guys out of Boston, Berkeley, of Harvard, MIT type people. And I'm sitting there with one of them, and then one of the other guys I was sitting with I was introduced to he was one of the original members of called to the Dead Cow, and they're famous for other reasons. And I'm like, wait a minute, he's he's the Loft, He's called of the Dead Cow. And now is probably when I should mention. The nickname for our hacking group at NSA came to be known as the Pit and So I'm a member of the PIT. I'm one of the founder's architects of the first penetration testing team at NSA, and we called it the Pit. So I'm like, it's the loft, it's the Pit. It's called it the Dead count Like, guys, let's get our picture taken together. So I had somebody take our picture, and I was like, you guys don't know this, but this is really historical because you know, dark side, dark side, white hat guy inside of the good. But you know, smart guys. Uh, nobody's nobody's uber that I've ever met. Most of the people that, especially from the early days, are all pretty humble. Yeah, you always you always hear about all the real elitist, arrogant jerks, and there are some out there, but most of the people that are really serious about this craft as it were, are pretty humble and pretty eager to share, and you know, love to swap stories and share stories. And I've certainly had a lot of great opportunities to do that. One of my idols, you know, one of our motivations back when we were forming the PIT, and we formed we when we were reorganized into this thing called Secure Systems and Network Attack Center, the SNACK, the Center of Excellence for Computer and Network Security. Back in nineteen ninety four, we got moved to a new building and we got moved to an office, and we nicknamed our office the Pit. And one of our motivators was a book called The Cuckoo's Egg written by a gentleman named Cliff Stall. Cliff Stall is like a you know Berkeley astronomer, you know physicists, smart guy, and he had noticed that by a matter of circumstances, that somebody was breaking into the university mainframe and stealing a lot of government secrets, because back in those days the only thing that was connected on the inter net was mainframes from the government and research university. And he set out to track down and find the people that were breaking in fascinating story, sort of invented forensics. And he documented his experiences in a book that's called The cuckoos Egg. Must read if anybody's interested at all in this discipline. A couple of years ago, again preat COVID. In fact, I'm going back to the same conference where I met Cliff Stall end of this week. But I was at a security conference up in Canada. He was the keynote. So like fanboy, I get to meet Cliff Stall and he's a goofy, quirky, weird kind of guy. He did a keynote presentation with a viewgraph projector. That's how quirky this guy is. Twenty nineteen Price probably don't even know what a view graph is, overhead projector. His his talk was a transparent transparency that he laid down on a box that lit up through through a lens that would project I mean, old school, totally totally geeky and quirky and cool. And it was. And I had to go up and introduce myself and meet him, get my picture taken with him, and I told him I was n s A and he's like, oh yeah, he visited NSA as part of his tale of trying to figure out how to hack catch these bad guys that turned out to be East German hackers. And uh, to my chagrin, the only time I've really been nervous to give a talk because my you know, he did the keynote, and I think I was the second or third talk after him. He's sitting in the front row, you know, one of my heroes. He's gonna sit and listen to me and give a talk. But that's how cool he was. I met the guy that wrote PGP, Phil Zimmermann, a couple of years ago. I've pretty much met all the pioneers at some point. And what's funny is a lot of those people because they got into it out of necessity. They didn't start out as computer scientists, and they didn't start out as programmers or administrators. They just had a job and computers became a thing, and so they wanted to learn about it and make it work to get something done. A lot of them went back to their day job. You know, Cliff Stall is still an astronomer or whatever he does, and a lot of these other guys that were a lot of university professors, university researchers, they went back to their first love. There's very few of the early rounded people that actually, you know, saw the dollar signs and went with it and came to a millionaires. To backtrack a little bit, do you want to talk about I mean, you mentioned it briefly why you ended up leaving the NSA after Even before that, though, you do have when when when we met at a conference, you showed me orders or or military wise I call them orders, but but a document authorizing you to do that? Was it the very first pen test of an outside organization. All right, it's the same question to the same story, Okay, And so I'll try to there's a lot. I have a lot of stories. I apologizes. Hopefully people are entertained. This is a podcast. People love stories, Jeff. All right, So I'll keep going and they can play me at one point five, which makes so you know, I'm in the pit where we're doing all these you know, pent tests of military basis throughout the world and and n s A facilities and other classified environments. And for what ever reason, And all I can say is is because I was the business major, I was sort of the I became the biz dev person and was trying to formalize what we did. I was the only one that was really interested in talking to you know, managers and suits and you know people other than just talking the tech and doing the stuff talking to the lawyers. So in doing all that, we were putting together a methodology and we were writing it down so it could be a repeatable process. It was something that had a beginning and end, and we'd take into account all the things we needed to think about before, during, and after doing the engagement. And somewhere along the line, I started working with some people from another organization called DISSA Defense Defense Information Systems Agency I think is what it's called, and they got me connected to some people at the Department of Justice and to part you know, everybody was just the Internet was new, everybody was plugging into the Internet, and everybody was like, oh, all the potential for the Internet. But then they were also saying, oh, but maybe we should think about security. So I went down into d C. This is nineteen ninety six. I was probably the first time I met him was probably April or May. Went down to the Department of Justice buildings, went into some big, beautiful conference room, you know, mahogany walls, big huge table, everything's wood. Meeting with these people and basically they wanted us to do a pen test of their Internet presence. And I'm like, yeah, sure, no problem, we can do that. Well, I go back and talk with the lawyers, and lawyers like, well, hello, time out. It's an unclassified network's that's kind of new and different. And NSA is responsible for the security of classified systems. But the organization that was responsible for the security of unclassified organizations at the time was nissed the National Institute of Standards and Technologies, and at the time that was kind of a tongue in cheek kind of running gag because NISS didn't have a whole lot of capability in any technical respect similar to the kind of stuff that NSA did. So I'm talking to the lawyers. I'm like, well, can we make this happen? And the lawyers like, yeah, we can make it happen, but there's hoops that you got to jump through. So we proceeded to go through several weeks and months of hoop jumping to make this happen. And one of the first things he told me was, well, you know, when you have this type of relationship, it's got to be sort of a handshake agreement between cabinet level positions. And I'm like, well, what does that mean? He said, what it means is the attorney Attorney General, which is what the DJ rolls up under, basically has to ask the Secretary of Defense for a favor and say, hey, can you have your guys come over and take a look at our systems. So you asked me to look it up I've got a copy of the original email, not email, I'm sorry, letter that came from the Office of the Attorney General saying, Hey, your guys have been talking to our guys and I'm paraphrasing it and basically we want you to well, I can read it to you. I'm therefore, I am formally requesting that DISSA and NSA work with us to provide a vulnerability assessment on the security posture of DJ sensitive systems and network connectivity to include the system network Architecture SNA and Virtual Telecommunications Access method VTAM. It's government. Everything's got to have an acronism. Also, the secure network architecture. Did I say that? All right? I am requesting that the assessment begin with the testing and evaluation of the security configurations in the financial Management Information System, which is used by several components within the It goes on and on. Pay a little over page signed by the Attorney General at the time, Janet Reno. You got that, Yeah, yep, okay, And it was actually addressed to the person that was designated within the by this Secretary of Defense at the time, the Assistant Secretary of Defense responsible for three C three I the honorable page jo okay. So that was the first step, and then what had to happen was, gosh, I hope I get this in the right order. This is a response from NSA. Of course, letters by the government, they're all written by peons like me, and they just eventually get up and signed by the people. You've seen the movies where they they throw papers in front of the president and he just signs them one after another. So this is a draft letter from m paid Age back to Janet Reno saying basically, we're on it. Then there's another letter that I have. This is from somebody at Diessa to the Department of Justice saying basically we're on it. And probably then the most interesting one is and it's had an official official processing form because it's got to have lots and lots of signatures to approve it. But this is the letter that was drafted by for the signature of the director of NSA. And if you see that there right there on the bottom line, I am the point of contact for this project, which says, yeah, we'd be happy to you know, members of the System and Network Attack Center will go down and do this. Now on the cover sheet, it actually talks about I think you can see this here. It had a it had a code name Project the effort is Project Eagle. So this letter, which is you know a copy of it, but it's signed and it's dated. You'll see the date twenty one August nineteen ninety six. Yeah, nineteen ninety six. So this is what happened. You know, of course, the letters signed, This is all going back and around getting all the signatures. It had not yet been delivered yet. I think the twenty first to August ninety nineteen ninety six was like a Wednesday or Thursday, the weekend before, and it's before the letter had been delivered. The DOJ website was popped first hack of add or government website rather famous. The hackers to face the entire basically replaced the entire website. They replaced Janet Reno's picture with a picture of Adolph Hitler. They had all sorts of more colorful things on it. And this happened like on a weekend, the weekend before this letter was going to be delivered and we were going to be golden. So I get a call Monday morning from my contact with the DOJ saying we had a problem over the weekend you know, we were hacked. I don't know if you heard about it, but help. And so I'm like, well, let me see what I can do. I hung up the phone and I called the lawyer's up, the General Counsel's office, and I explained to them what happened. And I said, you know, we're this close to being legal to going down there and doing the work. What do I have to do in order to get a team of people down there the next day? I mean, I want to help them out. They've had you know, you know, you know, they they're desperate, they need help. What can we do for them? And and they gave me three criteria. They said, well, don't go on your own accord, make sure you're sent by management, get the request in writing from the DOJ, and don't go alone. I mean that was it. I'm like, okay, I assembled a team I got I called back the DOJ and said send me something that requests this. I got it, you know, hours later. And then we went to our management and said, hey, this is what's happening. Will you let us go? And they said yes. So Tuesday morning we go down and we're looking at everything. Of course, in those days everybody had their own servers that were serving up their web servers that were part of their network. Maybe they were outside of their network, maybe they weren't, but when they were, when they discovered the breach, the DOJ admins, they took the systems down, took them offline, and wiped them and rebuilt them. So whatever evidence might have been there actually gone to begin with. Yeah, I mean there were no forensic guides, there were no rules back then. This is nineteen ninety six. Nothing had been written yet about how to do this other than Cliff Stall and the Cuckoo's Egg. But what he was talking about was mostly on phone lines and switches and pbx's public exchange servers all phone So we're there Tuesday, Wednesday. There were other systems that hadn't been affected, but we were looking for evidence of tampering and any footprints, as it were, electronic footprints to see if we could pull anything together. Were there Tuesday, were there Wednesday? We go down Thursday. Mid morning Thursday. I got a call from somebody back in the pit and they said, Jeff, the shit's hit the fane. You guys got to drop what you're doing and come back now. So we dropped what we were doing. We went back and got raided into the deputy director's conference room, and the lawyer that I had been working with for the previous year proceeded to read us the Riot Act and yelling at me, in particular for doing something that was potentially illegal that could get the director not only fired but prosecuted, and what the hell were you thinking? And I'm like, you knew about it well and technical. When I called the lawyers on that Monday morning, both the General counsel this guy and his deputy answered the phone and I said, I've got an issue. Who wants to take it? And the General Council deferred to his deputy. So I did this with the deputy General Counsel, not the main guy. But it's the main guy that was yelling at me. So I got put on double secret probation since I was the ring leader. And I first time I've ever heard of the church proceedings is when the lawyer was yelling at me, saying, don't you know you violated the NSA charter. Don't you know you could get the director fired if not prosecuted. I was put on probation. I was investigated internally. I found out many years later because I bumped into this lawyer after twenty some odd years at DEFCON. Ironically, turns out they were not only trying to fire me, they were trying to prosecute me as well. That is, that attorney or the administration director, the powers that being power. This was above him, and it was above me. In fact, I learned that, you know, I mean, I'd been pissed off at this guy for twenty some odd years for yelling at me when we were buds. And it turns out he was getting a lot of flak too, because he had ultimately sent us, or his office had sent us his deputy. His deputy resigned. But you know, after going on double secret probation and having to talk to internal security and tell the story and pretty much everybody I talked to like, that's it, you were just trying to help, it kind of soured me on continuing to work there. We eventually were exonerated, and we got pulled back into the deputy director's office and a bunch of the senior level management we're talking to us and counseling us, and they basically said, you know, we like what you guys do. We want you to do it, but if you're going to do it here, you have to follow our rules. So we said fine. I was gone from NSA by the end of September of nineteen ninety six, so like six weeks after this all went down, I was gone from NSA because it was end of the fiscal year. They had done it. They were doing a buyout to get people to leave. This is one of the fallouts of the Soviet Union and fighting for budget. They were paying people to leave, and we'd been kind of toying around a bunch of us. We're looking for you know, more more high paid jobs or in the private sector and all that kind of stuff. So I took the first offer that came along, and I was offered money to leave, and I got the hell out of Dodge and you know, end of September nineteen ninety six, you know, tried not to let the door hit me on the way out type of thing, which you know is you know, looking back on it almost thirty years later, if it hadn't gone south, I mean, you know, there was something cool and fun and patriotic about doing it there. You know, we were thinking we were doing a good thing. You know, there was the allure of more money out in the private sector. But I'll tell you what when I went out into the private sector, more than you know what I got an increase in pay. It was the idea that I could be hired by a company to do a pen test one week, do the job for the next couple of weeks, take a couple of weeks to write the report, you know, maybe a month later, come in and present our findings, giving recommendations, and we were done in and out, you know, maybe a month, maybe six weeks, whereas six weeks at NSA we would have still been trying to get permission to run the Pink Command right. So much more than the money was the lack of the bureaucracy and the more focused, less complicated there's a job to do, do it, report on it, give the feedback, thank you, you're done. Thing That was very refreshing. So but the reason I left NSA was because I was very much They tried to get me to leave involuntarily, but I kind of took the the opportunity when they when they when they gave it to me to get out and go out to the private sector, where largely I've had a more receptive audience of my clients over the years. You know, not every time do they want to hear what I have to tell them in terms of, you know, how they're insecure and what they need to do differently or what they need to invest in. But but generally, if you you know, if you can explain it to people, and I think I do a reasonable job of explaining to people why they should care, why they should worry, what they need to do to invest in or at least, okay, you've got limited resources, here's your options. You know, here's the pros and cons of what you decide to do or not do. So at least they have they can make an informed decision, or at least what I believe is a more informed decision about how to approach this thing that we now call cybersecurity and protect your organization. And oh, by the way, we're losing. And it's nobody can afford to do everything that they need to do to provide that mythical one hundred percent level of protection because it doesn't exist. And yep, we have a very burgeoning industry that keeps going and hundreds of billions of dollars are spent on technology, where what ultimately causes many companies to fall is a process issue or a failure of people in personnel to do something pretty trivial when you get down to it, how do you spending your money? People? How does you know when we look at the United States and we are we are a free content and limits on the government is a good thing. And and yet I don't want to say and yet as though we should erase freedoms in any way, shape or form. But how does the NSSA, particularly in this info second environment, how does the NSSAY compete against countries like China, Iran, you know, country Russia that do not have any moral compunction, any laws that you know limit their their government's reach. How do how do we compete against that? Well, that's that's a very complicated question to answer, and philosophically it does. And I just this came up a while ago in a conversation. I now have the opportunity to say it, so I'll say it. But I think it's one should think twice about automatically assuming that what we're doing is moral because we're doing it to protect us. I'll just throw that, just throw that out there, just to make people think. But generally speaking, you know, we are a moral, responsible society and government that does operate under rules, and most people take the rules fairly serious. There's always exceptions, and because there's rules and there's bounds, and more than that, there's just there's so much that could happen. There's so much that could go wrong, and you never know what's going to happen and where and where do you you know? Where do you where do you put your attention and focus and your limited resources. We're almost setting ourselves up as a as a society, if not pockets of industry within our government, which some would arguement argue that the government should be protecting it's it's it's not really a winnable situation in my in my opinion, whereas other countries, we are certainly told that they you know, aren't as strict on rules and regulation. And you know, I doubt if Chinese hacking groups, whether they're military or paramilitary or funded by the government, are going through a lot of procedures and bureaucracy and red tape just a perception. So I mean, we handcuff ourselves and of course you know, I work tangentially, I have relationships tangentially with a lot of people that are involved in you know, the mission of protecting the country cybersecurity, national defense and so on and so forth. To be honest, and if any of them are listening, I apologize ahead of time. But you know, given my experiance working with the government under the privactor, I've always felt that if you're working for the government, it's because you're not good enough to make it in the private sectors. So you're kind of second tier to begin with. And there are exceptions. I mean, that's just a very broad blanket, probably ignorant statement for me to say, but in my experience, the real cutting edge stuff happens in the private sector. And here's why. For better or for worse, in the private sector, everything's driven by the dollar. Everything is financially motivated. Companies exist because they're trying to make money. That's free commerce. That's what we do as a free country. And I often tell my clients in the private sector when they talk about risk and you hear all these words bandied about, like risk and vulnerability and threat security, I tell I tell my clients and anybody who listened. Frankly, you know, when I was in the I was working for the military. When I was working as a civilian, the idea of risk was all computed around loss of human life troops on the battlefield, citizens abroad and domestic uh, embassy workers, state department employees and stuff like that. But it all had to do with loss of life. In the private actor, it's all about money. That's very different, especially when everything you do comes at a cost, or everything you don't do potentially comes at a cost. So it's a different motivational factor. And I'm not saying it's a uh somebody posted on linked in, we're losing you just a little bit. I think your your signals a little low. But oh no, you can you repeat that last? Can you hear me? Now? Okay, how far last do you need to go? Just like the last sentence or two? Yeah. Well, what I'm saying is the the the idea of risk, why you do security, why you do the things. It's very different if you're you know, pursuing the national defense, which is basically lost of human life at some degree, versus the private sector, which is how much money you're going to lose or how much money are you going to spend or how much revenue are you going to lose or how much? You know, it's it's all a financial basis, and it's not that one is right and is wrong. It's just a very different and in a lot of ways. In the private sector, it's a lot better to understand dollars and cents, right, you know, that's a pretty easy equation to understand. In the national defense, oncept, uh, it's you know, how do you put a price on a human life? Right? And you know, right, I mean, you intuitively don't want to lose anybody's lives. But you know, I'm sure we've all seen reports or heard heard people talk about you know, you know, generals planning battles and and you know, even the Normandy invasion in World War Two, everybody knew people were going to die, right, and and the calculations that were being done on what what was an acceptable level of loss of human life given the potential gain? I mean, and that's where I defer to the people that do work for the government and do work for the national defense, because they do take that very seriously and it's very hard, but it's also very politically motivated, and there's a lot of there's a lot of stuff, bureaucracy and stuff that goes on with that, where maybe I'm taking the easy road out by just working in the private sector and it's all about money questions, Yeah, you know we do. But I want to ask you so, in your opinion, does you know the government is notoriously cheap? Right? The government is notoriously what they pay soldiers, what they pay case officers, what they pay NSA analysts and and and operators, what they pay their federal law enforcement like it is not for and for a lot of the jobs, whether it's a soldier or an FBI agent or whatever. There there are not a lot of comparable jobs on the outside, so they can so they can pay on the cheap when it comes to the NSA, though, you know, you guys may be a GS twelve or GS thirteen step five, but then you can turn around to mandate and CrowdStrike or crowds whatever and earn three times four times what you're making. Do you feel that the NSA needs to that the government in general needs to deal with this new reality and the NSA should pay people what they're worth on the outside in order to keep that talent. I mean, the short answer is yes, but it's complicated because and this is where I kind of do have a little bit of difference to the people that do you know, work for the government, because they do believe in mission and our patriots and things like that. But there but there is this stigma at the very least that if if they were really good what they did, they'd be in the private with the bigger dollars making them world. But that doesn't mean that everybody out in the pre sector that's making the big bucks is deserving of the big good. So you know, you might not necessarily want them deciding vis and who dies either, right, right, right? I mean I talked to a lot of people, you know, since I go out to a lot of conferences. I was at a conference last weekend and I was after I spoke, I was talking to probably a dozen college students that have come from one college, and they were just peppering me with questions and refreshingly, they did not ask change. When I talk to two students, how much does this pay? You know, how much can you make in cybersecurity? They're loosely at they have passion for technology, they have a passion for whatever this stuff is. But I try to tell people, you know, find something you like to do, find something you enjoy doing it. Don't get a hung up on the money, because you know you can make a lot of money, and that that arriving and making it. But I have yet to meet anybody that's happy and satisfied because they make ooh gobs of money. But I know a lot of people that really happy with what they're doing and really satisfied with their job. That some do make a lot of money, some don't make a lot of money. Some are in the government, some aren't in the government. But the happiest people I know are the ones that are doing what they love and feeling like they make a difference. And I think you can certainly. I mean, I've been doing the credit card industry for twenty years. You know, I go home and at night and fall to sleep thinking, wow, I've allowed a company to make money on credit card interests, you know, and contrast that with somebody that good night and fall asleep because they knew they helped save lives or you know, promote the national defense. So that you know, it's a hard it's a hard nut to crack, But I think there's a stigma that if, at least for me that if you're for the government, it's because you could in the in the in the private sector where they pay the big bucks. Of course, a lot of people put their time in in the government and then they get the posh job at the big companies out in the private sector. And you know, most of the people you know and see, and man, I'm grossly generalizing. I'm not impressed by the people that you see the public figures, the ones that are always getting interviewed on CNN and all the different news channels. Yeah, and so on and so forth. The people that really are good at doing all this stuff that and love it and are passionate about it. You don't know who they are. I don't know who they are because they're just in the trenches doing it and they're doing it for whatever makes them satisfied. And you know, God bless them, because you know, we need those people. I think it's interesting because you talk about the mission, and I can see how similar to the military, the people in the n essay have a mission and a purpose. And as you experienced, I think the challenge with the mission and patriotism and that sounds a the only thing that stands between that and bitterness is like one bad manager, one bad leader, and they can they can steal that that entire sense from from a person. You know, how is the NSA when it comes to their leadership development and their management development things like that, Yeah, I don't. I don't. When I was there, which was you know, for the better part thirty years ago, there was a stigma between you know, if you want to advance in your career, go up the pay grade ladder. To get beyond a certain level, you had to get into management. So you had to go there was either the technical track or the management track, and the management track is who made the big bucks. But you know, if you were good at the technology, and I use that term loosely, technical could be your cryptologist. Technical could be anything, but technical not management, you know, labor not management. The people that were really good at it and wanted to advance at some point had to kind of suck it up and like, well, if I want to go further, I got into got to get into management. I don't know that they've completely solved that. I was actually invited back to NSA last fall for an alumni open house because they're basically trying to recruit people that used to work there because they're hiring there's certainly a need, and we talked about how they don't pay well, and someone like me who his parents expired over twenty years ago, I simply asked, is there any way to streamline me getting back in you want me? I'm certainly capable. I certainly have a lot of experience, but there's that background investigation and getting the again. And the very long winded answer that I really never got a good answer was no, there is no shortcut. I was. I think I was at RSA a few years ago and I went to the NSA booth because that's sort of a pilgrimage every time I go to RSA conference. And I met a young lady at the booth and she's like, oh, you're Jeff Man. I'm like, oh, she knows who I am. She knows my stature in the industry and my background and stuff. And she said, oh, I used to go to school with your daughter. So I'm like, oh, okay. So she had no idea who I was other than I was the father of a classmate of her. So you know, my daughter now is in her early thirties, This woman's in her early thirties. She's senior level management at NSA, and she might the smartest person around. But my gosh, I mean thirty, you know, early thirties, probably has been at NSA since college, so she's got maybe ten years experience, and she's in a really senior level role that doesn't give you warm fuzzies. And it's nothing personal against her, right, It's not because she's a woman, it's not because she's young. It's because she's got maybe ten years of experience, and how much of that ten years has been off on the twenty twenty program, getting more education and training and doing this, that and the other. And my impression is they're they're working with what they've got to work with, right, And again, it's nothing. It's not a knock on her personally. I'm sure she's you know, she seems to be very smart and very wonderful. But she's made comments about how NSA is on top of their game. At this open house, the director was talking about how NSA is on the top of their game, and he's a very compelling speaker. But I'm like, yeah. Then I started talking to some of the people, I'm like, yeah, you're still full of it. And that's just my opinion. So that you know, they talk a good game, but at the end of the day, it's still a government job and they've got lots of stupid bureaucracy and rules and regulations. And because they're sort of the you know, only game in town and they sort of look inward, they don't see what the big picture and they don't see the out sid I've been trying to offer them. Hey, I've been out in the private sector for twenty five, twenty six, twenty seven, twenty eight years now. I've learned a few things that maybe you you say, we want to be more engaging to private sector, why don't you bring me in to let me tell you how to to maybe do that, because you know you're you're me first approach, we're NSA. You should listen to us. It's not going to cut in the real world because people are like, yeah, you know, oh yeah, you're in. Say what does that mean at the end of the day, and gosh, I hope I'm not getting fired or rest of that. And and one last question before we get to like fewer questions, I'm curious about you know, like you know, when when back during the naval era, when you had the letters of Mark, you know, during you know, when we've had these times when the government can control and you know everything, we had the idea of sort of private tiers. Do you think that in this cyber warfare world, in this cyber environment, when when there are fourteen year olds who are just brilliant and doing crazy, you know, amazing stuff, and you know there are groups out there, do you think that the government in this one arena should turn to like a privateer model. It's an interesting question. I would say. I was having a conversation in the last couple of weeks with some people at one of the conferences I go to, and they were talking about Actually it might have been on the podcast I do, but they're basically talking about how, you know, there's certain hacker groups out there that are just going after certain not necessarily nation state actors, but you know, sex trafficking, child trafficking type of groups. You know, there's conscientious hackers that just kind of go after them just because it needs to be done, and it's not technically sanctioned by the government, but sanctioned by anybody. But nobody's really complaining so I mean that's my most recent frame of reference. I would say, I don't my bias is NSA or the government puts its fingerprint on it, it's going to get stupid at some point. Could could Could there be sort of a handshake unofficial Well there's this shadow group out there that's just doing the responsible right thing. Uh. That might work for a while. Of course that could go wrong for many reasons too, because you know, absolute power corrupts absolutely. But you know, the serious hackers out there that are socially minded, you know, socially conscious, want to do the right thing and are frustrated at bureaucracy and the limits the government puts on out of necessity, but it makes it very difficult to do what needs to be done in a fashion or a manner that canon should be done. Yeah, I would you know, I don't know what you would call it. If you would call it privateering per se or just looking the other way? Does there need to be some oversight? Does there need to be some kind of stop gap? But I could see that happening on the other On the flip side, do I believe in vigilanteism? Not necessarily? That sounds intuitively wrong. But I mean anything, anything can work for a while, and anything can go south when the wrong personality and the wrong motives come into play. You know, often ask about hacking back and whether that should be done by companies, you know, or leave that to the government, and right, yeah, you know, this is where it kind of you know, the difference between the private sector you know, money that's the risk, and the government protecting the you know, the US and US entities and things like that. That's where it gets a little bit fuzzy for me and tricky. But I I tend to want to like, I'd rather have the government in control of the actual war fighting because that's sort of what they're in the business of doing, because I think it could get real ugly and lots of bad things could happen to innocent people if it's done by the wrong people for the wrong reasons, or even the wrong people for the right reasons. But outside of the boundaries of control, Yeah, there's a reason why we have a Geneva Convention, which you know, it doesn't make sense at some level, like why do we have people sitting down coming up with rules on how to conduct warfare? At some level, it makes perfect sense in another level, it's a head scratcher. It's the same type of thing for hacking and hactavism of stuff like that. It makes sense at one level and at another level it's like, man, you don't want to go there. That's very sketchy. And I can go either way depending on my mood and depending on what the situation is. So so again, I'm sorry, but one more falling question, because you mentioned that you need to convention, and I'm curious in your experience, if a non state actor, you know, a hacker group, shuts down a hospital over ransomware, should they be considered a viable military target. Hmm. It's an interesting question from a Geneva convention perspective. And again this is a conversation we had on our podcast a couple of weeks ago with a gentleman named Josh Corman. You know, it used to be that the hackers sort of had the bad guys. You know, hackers can be good or bad, but the bad guys used to have sort of a code of conduct or ethics that you wouldn't go after, you know, like a children's hospital and hit them with malware or ransomware. But the perpetrators the bad guys that are doing this, they're looking for targets of opportunity. They're not looking at who it is as much. So there, you know, there is this idea that you know, there used to be some idea of responsible crime, and that kind of can go away at some point. So are they should they be targeted by a military action? I would tend to say yes, But again, that's the situation where there's private groups, there's hacking groups, you know, good guide groups that are actively targeting those types of organizations and doing what they can to take them down in a in a logical, technological sense. I don't think that it's in a military sense, in a physical sense. But yeah, there's certain lines that get crossed that most people will say, Yeah, that's something that shouldn't be done. That's not cool. And it used to be that there was responsible criminals that wouldn't do something like that, but that seems to have gone out the window. So, you know, whatever works to get the stuff to stop happening, I'd be tempted to condone that to a degree if that makes sense. I agree with you. I mean, I'm just curious. I mean, you're you're the expert. Here. But I feel as though if in according to Genene convention, if they're response for the loss of life, they're a viable target. But I don't know from cyber perspective somebody has experienced as you what what your thoughts would be, All right, let me get well final comment on that. I mean, what's interesting to me is we're again we talked earlier about some things are kind of coming full full, full circle or overlapping. Maybe this was off the air, but you know, signals intelligence is becoming a thing again. The idea that risk now because we're targeting hospitals, they can't afford the security, can't afford the ransom, critical infrastructure, you know, the the idea of the risk being lost of human life is kind of becoming a thing that's more tangible and real in the private sector. So it's it's not a it's not a full circle thing, but it is a is a blending where more action is required and more action from the government is neces, even if that means regulation and regulatory compliance but also assistance. So it is an interesting time we're living in. But I think it's interesting that risk in the private sector, which has been money for so long is now starting to be human life again, which is something that the military understands, so yeah, maybe they should step in. So viewer questions. M Corbyn, thank you very much, really appreciate it. Does bitcoin have a future as a tool for power projection in the future? And also, what is your take on the two thousand US China hacker war. I try to avoid bitcoin as much as possible. Does it have a future? No comment, and I haven't heard of the other one. I don't do a lot in the technology realm. I focus more on people and processes. So that's just a general disclaimer, so try to ask me another question. I'm sorry I can't answer the first one. Johnny, thank you very much for the donation. I don't see a question. If you have one, please throw it in the chat. Oh I see another one. Global Media, thank you very much. Support the teamhouse, get those likes fs everybody. If you haven't liked this, please throw us alike and hit us and subscribe if you haven't. Johnny, thank you very much. I wonder if Jeff thinks CPU architecture can be secure. Intel, Apple TSMC have been shown to have unpatchable physical vulnerability in chips, which leaks secure keys. Yeah, I had a chief scientist I believe it was in my early days at NSA, so it would have been in the eighties maybe early nineties that used to have a mantra, what can be created by man can be broken by man. So and that context, you know, can CPUs ultimately may be made one hundred percent secure unbreakable? No? To me, there's we're having two different discussions that often get lumped under this this mantle of cybersecurity, and that's the idea of securing all the things as much as possible, So securing creating a secure state, which is kind of a noun. And then the second thing is security. What do you do given you can't do the first what do you do to monitor and detect and respond to your network, your environment given that something inevitably is going to fall in terms of the technology. So in that sense, what I'm saying is, no, I don't think CPUs can be ultimately secured one hundred percent. But given that, what do you do? Maybe you don't invest as much on trying to find a better CPU. What is done to these days by the organizations that you referred to is probably good enough for most people. But it's that the few that care and the few that are going to be impacted the most by somebody that figures out a compromise, figures out a way around to work around what we used to call a feature. They're the ones that need to care about it, but they need to know how to detect it, to minimize the damage, and to respond to it. I am a proponent of the process. Security is something you do. It's not a state that you achieve. There's making things secure, and then there's security, which is the diligence and the monitoring and the standing guard and standing watch so that you see the attack when it's happening, intercepted early, minimize the damage. That to me is the essence of security. Do you think that hardware manufacturers and software manufacturers are transparent enough with like the community in terms of what they think the weaknesses are so that people can be diligent or do you think they could be more transparent? Short answers, No, I don't think there as transparent as they could be. The podcast that I do Paulsecurityweekly, Security Weekly dot Com, Paul Asidorian the Paul and Paul Security Weekly. He works for a company that does hardware hacking hardware vulnerability research company. Well, I don't need to say your name, We'll let him do that. Go to security wiky, you'll figure it out. But he focuses a lot on hardware vulnerabilities right now. So that's a topic that comes up a lot in our podcast over the last year or so, and he he reports very routinely on the research that he's doing with his day job on the insecurities of hardware and how hard it is to secure hardware. And it's not really the new frontier because it's been around forever. I mean I worked at NSA when it was all hardware and there was no software. So you know, it's semantics, it's blurring the lines. But you know, hardware is also prone to insecurities and vulnerabilities and bugs and weaknesses and misconfigurations, and they're out there. They typically don't become publicly known until either somebody exploits them or some research or discovers it, and then it's you know, the sky is falling. You have to temper it with you know, the likelihood that somebody's going to go after something like that, going to go to that degree of attack that they're going to try to exploit that. A general principle i'd say is, you know, the bad guys are going to do whatever works, whenever's the easiest. I mean, they have their own cost benefit analysis, as it were, So they're going to do what's works and what's easy, and they're going to hit the targets that are vulnerable. They don't necessarily target specific organizations, which to me is one of the big eight pound gorillas in the room is that we have this industry that makes people protect against all sorts of stuff, but most of the bad guys aren't targeting specific organizations. If they did, they sort of have unlimited resources and they could go after from any way they can, and they can take the time, and if it means exploiting a hardware vulnerability, they will. I think the line is drawn when the hardware of vulnerability it can be exploited in a way that is sort of reproducible, and it can become something that's you know, random in terms of let's find somebody who's vulnerable. We don't care who it is, right even if it's a children's hospital, and let's exploit it and make money off of it. Uh, commodity you know, commoditize types of attacks that that you target anybody, no offense, it's just we're just targeting whoever is vulnerable. Do you think that ransomware is a service has has kind of like increased that type of tendency that you know, you might have ransomware gangs that do have those codes, But then when it's ransomware as a service, you just have some script kitty out there who's like, ah, fuck it, I'll just find whoever whoever will pay well. I mean, it's simple economics, and it's it's you're not really paying attention to the who the target is. It's whoever is vulnerable that you can make money off of. I mean, ransomware in general, I think has changed the dynamic of cybersecurity significantly because you know, the way I was classically taught about this problem which we back in the early days we call data security or information security, and most people have probably heard of the CIA triad, the three components of security of data being confidentiality, integrity, and availability. So confidentiality, keeping secrets, secret, integrity knowing that the data is valid, you know it hasn't been altered or tampered with, and then availability can you get to the data when you need it. Most of this cybersecurity industry, which is mostly technology based, focuses on the confidentiality problem, trying to keep things secret, trying to keep things safe, trying to keep things inaccessible. In terms of stealing it, you know, nihilist service has been a problem off and on. Distributed to denial of service has been a problem off and on over the last twenty years or so. But we sort of solve those problems integrity issues, faking the data. If you trust the data, that can kind of come into play with phishing schemes and fraud schemes, scams and stuff like that. But availability, that's something that we haven't really invested a lot of technology solutions in it, and every believes that believes that technology is how you solve the problems. And it's even more twisted than that, because it's not just ransomware where we're going to hold your data and if you don't pay, we don't give it back to you and you lose access to it. But now it's sort of the I don't know if somebody's come up with a good term for it, but holding the data and threatening to release it right rather than just sending it back to you. So sort of I don't know what's a good term for it, but you know that's coming up more. Yeah, kind of a black man. Yeah, yeah, you know that there are no good there are no good technical solutions to prevent that, other than the things that we've been preaching for the last thirty years of sort of basic security hygiene to try to to you know, prevent that stuff from happening. I mean, we don't with all the ransomware attacks that are out there, you don't often hear people talking about how the ransomware attack was launched in the first place, how how it you know, got into the environment. But it's usually a phishing attack, which is not a technical failure, although you could argue that it could be why am I getting an email in my inbox that's got a phishing link in it? Why isn't there technology out there that filters that or blocks it? But there's that aspect of it. But you know, we we don't have a lot of good technology out there that prevents people from clicking on a link or falling prey to a really really convincing lever phishing scam or or you know to date myself back almost thirty years to open an attachment of a document in an email that I got from a trusted source that says, hey, read this, and by doing so, I've launched a virus or malware what we used to call viruses and trojans and malware, but what we pejoratively call ransomware these days, right well, I mean, in these days and times, it's amazing how many organizations aren't even enforcing basically two FA like you know, a to FA to log into stuff. It's incredible that basic steps that aren't being taken. Often I agree with that, and what I often shake my head out is the fact that while there's so many vendors out there that are trying to sell you convincing solutions, there's for and I'm talking primarily the private sector, because that's where I've been most of the last thirty years, without regulation, without compliance. Most companies aren't going to do it because why should they. They don't have to, and until they get popped, until they get breached, they don't get the religion of we really should have done that. You know, I've been doing the payment card industry for twenty years. It's the PCI Data Security Standard is a pretty decent, high level set of rules of things that you should do to secure your organization, your network, to protect data that you care about being stolen. You know, specifically it's credit card information, but you can apply it to anything. Most organizations that I work with are doing it because they have to, and in the early days, they weren't saying. You know, even before PCI, when I was working with companies in the private sector, and even in the beginning days of PCI, the questions I was being asked from companies that I worked for was what do we have? They weren't asking what do we need to do to be secure? They were asking what is everybody else doing? That's a peer in my industry, So that you know, I can do is as little or as much as anybody else, so that when something bad happens, I can say, well, I was doing best practice and therefore not get fined or not not be held liable or accountable because it could happen to anybody, and it could happen to anybody. It's a weird it's a weird dynamic. But most companies out there, if they don't have a reason to do it, they're not going to do it. But you can sort of explain that in a financial model because every things, you know, money based in terms of the risk model, Well, it hasn't happened yet. Why should we spend something on you know, spend money to protect against something that hasn't even happened yet. So there's a there's a there's a financial logic to it. And of course it blows up when the bad thing happens, and that's when we get called in and we help them straighten things out, and uh, you know they get religion. But but you know what what's in the news these days in the private sector critical infrastructure utility companies I you know, and people are talking, you know, I hear people talking about, well there's there's this this and this that minor attack framework, and do this and that and the other, and there's all these things. I'm like, there are a utility somebody in that company is is, you know, collecting credit cards to pay for the water bill, the electric bill. So they know PCI is in there somewhere. If you just did what pc I said to you, you'd be you'd be pretty much okay. But nobody seems to be connecting the dots on that PCI is this. Oh, nobody likes to talk to PCI. That's old. It's stupid, you know, it's it's not flashy and new and shiny, but it is today because pc I four point zero is now the law of the land. Do you have anything else for? Yeah? How long do you think it will take? Thanks Sean Jones. How long do you think it will take for AI based security controls to become as calmplace in the private sector as Layer seven firewalls are today? Oh? God, AI the latest buzzword thing that I'm trying to avoid ever dealing with. You could probably map this to other things, like you're you're you're using the firewall is the analogy. Everybody's got a firewall these days. I'm sorry they don't have firewalls anymore because they're infrastructures now in the cloud and it's protected by software. Ten years, with a little bit of acceleration, I'll say five years, that's my guess. And then from Corbyn, Oh, justin Zulu, thank you very much. What are some things that average person could do to protect themselves going forward? Probably the biggest thing is put what the industry calls multi factory authentication what we used to call two factory authentication on everything. I'm not a personal fan of password vaults because I'm old school enough to think that you shouldn't put all your secrets online period or rely or trust technology period war Games nineteen eighty three, don't trust the whopper, but use a really, really really long password. And I would even advocate uh phrases poems, song lyrics. Try to think of obscure song lyrics and then apply random you know, upper case, lowercase special characters everybody knows to substitute, you know, the number four for the letter A and the number three for the letter E. But don't do it on the first letter, last year, last letter, don't do it on every letvel letter. Put spaces in between the words, or better yet, put spaces in between somewhere in between the word and not between the words, because that's gonna that's gonna protect against password cracking, brute forceing. But more than that, I would say, make sure you're always using some sort of multi factor authentication on everything. There's a lot of there's a lot of a lot of people talking about using password vaults, and you get to is a super long random password generated things that are stored in the vault. But password vault companies have fallen victim to compromise, so they're not a perfect solution. In fact, I interviewed the CEO of Last Past last summer at Black Hat as part of the podcast I Do. We did live interviews of executives. That was an interesting conversation. I didn't know the guy wasn't the founder of the company Last Past. He had become CEO like an October, you know, two years ago, you know, months before they had not one but two major breaches. So I was kind of like ouch. But I mean, I'm old school. I don't believe that you should put all your eggs in the technology digital basket. I think this is your best tool right here. My current domain password from my day job company is like I think, it's like thirty eight characters long. It's a song. Leir's a it's a line of a song that's you know, a song that I know, and I mix it up a little bit enough to just protect against the cracking, but just the sheer length of it, thirty eight characters, nobody's going to guess it. Even if I would even say if you knew what album I was citing a lyric to. Because of the various permutations, Yeah, you could compute it a brute force, but it would take you a while because I mix up the spaces and the upper characters and lower characters and special characters and stuff like that. So but because I grew up typing with ten fingers and not thumbs, I can type my thirty eight character password in faster than probably most people can do a ten or twelve character password. They're just doing it like this. That's just me being a being a crotchety, curmudginy old timer. Get off my loan. So, Jeff, my question, because I do use a password vault, like my question to be in this in this digital world where everything we do requires a password, and obviously you don't want to reuse the same password, But how do you manage thirty passwords without a vault? Do you write them all down? Do you personally just remember them all? Like? How does the average person manage that? Well? A, I'm not the average person. Yes, for better for worse. You know, we used to talk about having passwords you care about, and passwords are the throwaway passwords. Of course, I've talked to developers that you know are doing stuff and you know Azure aws where they need to know like three hundred passwords for all the various different systems that they got working on. You know that that can be a little bit excessive, But I guess I'm more of the of the mindset that you have the throwaway path, you need to make a password, have a decent but have But I'm okay with repeating passwords for accounts that I don't care about, now that you know the the the thinking on that is, you don't want to use a password multiple cases and use it on someplace where something's going to get stolen, something you care about. So I sort of distinguished the throwaway password. Oh I've got to sign up for something, I got to create an account. I'm never going to use this, need to have it. I need to have a password, so I I have a I have a I have a throwaway password. That's just something lame. And then the passwords on the accounts that I care about, which are much fewer, they're either unique or there are permutations on a very very long stream, you know. But the there's a couple considerations to be made, and I can argue myself out of this, because it's not just stealing the hash and cracking it and trying to figure out what the password is. There's if you're using it multiple places and it gets compromised in one place, it can be used in many other places. That's another type of attack. There's the possibility that you know, even your best passwords somehow gets intercepted in while you're using it, where it's in a fashion where it can be copied, you know, more more rare, but still still a possibility. But the bad guys don't often do it that way because there's easier ways to do it. So I guess I'm I could be proven wrong. I'm happy to be proven wrong and argued out of it, but I'm still of a mind that I have throwaway passwords that I'll use repeatedly in many places. And I don't care if you knock over this account in that account, in that account, in that account, because I just set up the account so I could download the white paper, damn it and read it right. But you know, I mean shoot my rental car company that I use, and I won't say which rental car company I use. When I initially set up the password on my first app they asked for They asked for a PIN. So I have a four digit password on my car rental company and I keep thinking I should change it, but then I keep thinking, but I don't really care if somebody rental car in my name because I could probably sort that out. You know, I'm not going to be ultimately held reliable for liable for it, and who's going to do that anyway. So I have a four digit PIN that is my password in my car rental company to this day. And I said it probably twenty five years ago. Us. Tell us about your podcast and where like people can go to find it. Sure, I'm on a podcast call Paul Security Weekly. You can find it at securitywekly dot com and if you search on all the podcast catchers, and I think we're on YouTube and twitch. Securityweekly dot Com is the way you'll get there. For subscribing. Paul Asidorian is the Paul and Paul Security Weekly. He started the podcast with his friend Larry Peshe back in two thousand and six, I believe, so it's one of the oldest security podcasts around and it was built on the premise of practitioners just sitting around having drinks talking shop. Paul's a cigar smoker, so much like your studio there, the liquor flows freely. The cigars are smoked. And I met Paul about ten years ago when I went to work for this vendor that was a friend of mine and he got me involved in the podcast. I've been doing it about nine years now. But we're a weekly podcast. Paul actually made it his own company at some point, which was acquired at some point, but it's a it's a network of shows. We drop about probably ten hours of content a week. There's Paul Security Weekly, the Flagship Application Security Weekly, Enterprise Security Weekly, Business Security Weekly, and twice weekly security news segments. Lots of content, but the people that at the end of the day are practitioners that are in this because they're passionate about it, and we talk shop. We talk about all sorts of things like we've been doing tonight, and for people listening, we'll have a link in the description to go and check it out and where else can people find you? I do a lot of conference speaking to this day. Thanks to my friend that pushed me out into the into the into the conference world. I'm going to be I'm actually going to be up in Canada later this week at a conference called Atlantic Security Conference. Atlantic Security Conference, I'll be at B Sides Harrisburg, Pennsylvania in two weeks. End of the month, I'm going to be in Boise, Idaho at the Boise Issa Conference. In May, I will be in Saint Louis at the Show me Con Hacker Conference. So a lot of conferences. I'll be around for what we call Hacker Summer Camp, you know B Sides Vegas and Blackat and Defcon. I'll be out in San Francisco for RSA. I'm on Twitter, although I know nobody's on Twitter anymore, but you can find me there at mister jeff Man. You can if you spell my name right. You can find me on LinkedIn. Go to YouTube and type in my name and security and you'll find many recordings of talks I've given my NSA days. I my first couple of years where I was in the crypto shop, I did a talk and I had the marketing team come up with a sticker for it, because hackers love stickers, so I think Tales from the crypt Analyst. And then when I did the talk about the NSA Red Team the first pen testing team. That was the sequel more Tales from the crypt Analyst. And this year I'm giving a talk and commissioned new art. I'm giving Tales from the crypt Analyst. The Afterlife. We throw stickers up on our door. We want as many. We want as many of those stickers as we uh, one of each. Yeah, if you have them, we love, we love to I'm gonna have to get more of these made, more of these made, because I'm down to the last couple. But the the woman that was responsible for all these stickers, uh, her Twitter handle is one dark one. She does a lot of graphic art for a lot of the hacker conferences and the b sides, so I call her a con artist. Literally, I have I have two more questions real quick anyway, and and D might have some from Patroon but and gorbyin thank you very much any way to circ event hackers for hire used by foreign nations, pay them more. Uh, Mohammed Savani, thank you very much for the very genest nation. Uh do you so there's a couple of questions. Do you like U be keys for passwords? I've not used them, but yes, I think they're a good thing. To do if you if you want to drop the money for him. Yes, seriousness of quantum hold on, sorry, I lost that seriousness of quantum compute threat and we'll get there. But like any other technology, uh, it'll have the potential for being used for good and bad. So in the old days of the Cold War, it was often to the Cold War as a game of cat and mouse. You know, the Soviets would do something that would be devastating, but eventually we'd figure it out, and then we'd do something that was devastating and eventually they'd figure it out. So kind of this cat and mouse game. I think the same is roughly true with all the technological advances, quantum being that what we were talking about a year ago. But of course AI is the thing now is that everybody's talking about. So has the potential for good, has the potential for evil. It's overhyped and not there yet. The quantum thing is becoming real. But you know, until quantum is computing is available on the smartphone or reasonably affordable by people that you know aren't nation state status, you know, it's not going to be an issue yet. What's interesting though about quantum, I will add, is because quantum has the ability to break things when it becomes popular. That is stuff that was even encrypted in the past. That's where you start have to think about now what you're protecting with the current cryptography, especially for stuff you're storing, because it could be cracked in the future by quantum computing. So think about what you're saving and thinking about why you're saving it and storing it. And keep in mind that what you're storing now, based on what algorithms you're using to store it, could become susceptible compromise. But like everything else security related, maybe the protection isn't just coming up with a stronger algorithm. Maybe it's preventing it from being stolen in the first place, or if it does get stolen, you catch the people doing it and prosecute them. I mean, there's always more than one way to solve the problem. There are no single point solutions. Quantum included, AI included for Okay, we've got this, that we're done, we're good, we can we can walk away now and not think about it. Right. How best and this is still from Mohamasvanni, how best developed US talent earlier like Unit eighty two hundred and I think this goes into maybe the idea of when when obviously there's there are a lot of legal things people can do now to develop their hacking skills unlike the past. But let's say you have a kid who is curious, maybe with a criminal bent, kind of a n'ar do well, but reforms his ways. Is there a way do you do you feel like there's a way to bring these these people into the government. Well, not speaking for the government, I would say yes, but you know, the government has rules. I mean I had, you know, when I was hired at NSA, I had to go through a background investigation. I had to go through a polygraph. They wanted to know all your deepest, darkest secrets. And they they claimed at the time it wasn't necessarily if you had done something in your past it would it would mean you didn't get hired. They just wanted to know about it so you can get blackmailed in the future. Right. So, I mean, I think the government's getting smarter at knowing that they have to sort of cast a wider net and not necessarily go after the cookie cutter stem person. I mean, I'm the living proof of that, you know. I wouldn't. I was not a critical skill, I was not a STEM person, and I was hired by NSA and I did some things that were meaningful, and I probably wouldn't be, you know, given my GPA and given my educational background. If it wasn't for those aptitude skills tests recognizing my potential, I would not have been hired by NSA then or even to this day. So what I'm trying to advocate for is, let, you know, let's figure out a way to find the people with the potential and the aptitude that aren't necessarily the cookie cutter. You know, they're they're in a STEM curriculum, or they're from a certain neighborhood, or there are certain skin color, or there are certain ethnicity, or there a certain orientation. Let's find the people that have the potential and the aptitude because they test well in a certain skill set, and let's promote that. That to me transcends all the other issues. And I'm I'm the living proof of that because I had no business being hired by NSA if all they were looking for was computer scientists, engineers and mathematicians, because it was neither of the three. But I ran circles around the people that they hired that did have those degrees, that left after three years with a graduate degree and went off and made a lot more money out in the private sector. Right. We have a couple of Yes, I have a chip on my shoulder. We have a couple of questions coming in, so I just, uh, I just want to make sure we get to them. Thoughts on meta uh matter most messaging, you know, not sure I know what that means is. Yeah, I think it's a new secure signal like signal style. I'm not sure of it. Also from Mohamed Savani, how much difficulty difficulty does a red teamer like you have keeping up with a relentless pace of development and knowledge needed like networks, t VMS, to osend to CALA, the nex tools, et cetera. So I don't do the red teaming anymore anymore. I hung up my my hat on my gloves on doing that about twenty years ago. I've been for the last twenty years trying to talk to people about the possibilities and what could happen and what could go wrong and what they need to do to prevent it. From a process perspective, Rather than keeping up with the technical stuff that being said, because we talk about this ad nauseum on the podcast, because I'm other co hosts are actively red teamers when we do get down to it. While the technology has changed and the techniques necessarily changed, the underlying motivations and methodologies, the foundational principles of security have not generally do not change, So in that sense, I don't need to keep up with it because nothing has changed. And then you sprinkle on top of that for all the stuff that's going on. The number the two reasons why companies still get breached, the two most common reasons why companies get breached to this day, to this day in twenty twenty four is something to do with weak passwords or stealing passwords, exploiting passwords, and the exploitation of trust relationships. And those are two broad terms, but you know, very rarely is a technology related I mean, we were talking about vulnerabilities and cve sports a couple of weeks ago, and you know, the the statistics for something like only three percent of all the published cvees have ever been used by bad guys to steal something, to exploit something. And yet we have an old industry built around driving down the vulnerability count, driving down the vulnerability count CVEE CVE Yeah, and so the cvees what you mentioned, are the critical vulnerability like that they come out through the various like Microsoft hatherser is it CV tuesday or Wednesday? I don't remember, but basically, well, it's patch Tuesday. The CVEES is common vulnerability. What's the E stand for? I can't think of what it is, but basically, I mean, what we're really getting down to is most companies are running a vulnerability scanner of some ILK and responding to the results, and the results are ranked critical high, medium, low based on some sort of statistical calculation which is called a cve score, and it's got lots of different factors involved. But and I'm somewhat generalizing, but my almost thirty years of experience in the private sector, most companies jump at the scan results and not anything else that they do in their security program. And so the argument and the discussion we've been having on our podcast over the last couple of months is what happens when a vendor discovers a vulnerability and something that they produce because somebody discovered it and disclosed it, whether they got a bug bounty or not, but they told the vendor about it, and the vendor decides to fix it, but not issue a CVE. Does it ever get to this scanner, does it ever get a finding, does it ever get a ranking? And do companies ever respond to it by doing the patch or the version upgrade? That I think is a very serious issue from the perspective of most companies. They've had it drilled into their heads that everything starts with what is the vulnerability scanner tell us to do? Because everything we do is associated with driving down the vulnerability count, because that's how we manage risk. Overly simplistic. Wrong And we could go another couple hours, right, but we shouldn't another one. Mohamed Fvani, thank you very much. Final, Finally, for the lads, how much difficulty do the glowies? I guess that's the new slang for FEDS have in tracing Monaro transactions. Beautiful algo lol. Asking for friends, of course, Mohammed, we're all asking for We're always asking for friends, sure, but when it comes to crypto, you know and stuff like that, a lot of people have this impression that it's anonymous, but it's really not. Can you tell us a little bit, you know, from your experience or from your knowledge, like how how do the FEDS track Monaro or bitcoin or anything else like that. I mean I can't speak definitively because I don't work with them or for them anymore. But given what little I know about it, you know, if they're motivated to track it, they can track it. There are ways to do it. Uh. I would hesitate to say that they're tracking everybody just because because they're financially and economically bound just like everybody else. But if they have a reason to go after you, the the indicators are there. I mean, if you're asking are you safe to do it? And the government's not watching you, you know, I think a certain amount of big brother fear. It's probably healthy, but you know I would I wouldn't lose sleep over either. I think. I think one of the you know, and and uh, you know it was Darkseide Diaries, Jack risor actually you know, recommended you to me and in one of his episodes he had meant they talked about a Department of Homeland Security operate against child pornographers and how they tracked you know, the crypto going in and the thing is they may not be able to track like crypto in terms of where it's going inside the system, but eventually you got to cash out and they can follow it to that cash outpoint. They can follow it from the bypoint, they can follow follow it from the cash outpoint. So so I think, you know, just kind of emphasizing on your point. If you think you're getting away with something, you're probably not well. I mean, probably a similar analogy is, you know, encrypting data, and data was encrypted initially for transmission for communication and the mantra back then, or even if you're doing it in the modern world for storage. But if you're encrypting data to protect it, sooner or later you're going to want to decrypt it so you can use it, or you can refer to it, or you can act access it. So the attack points are either before it's encrypted or after it's decrypted. So I think that's the similar analogy to what you're painting. Jack Reesider saw him and Schmukhan, that's probably where you saw. I'm episode eighty three. If anybody wants to go listen to it, I'm the second part, second half of episode eighty three. It's entitled NSA Cryptologists. I met Jack again at def Con a couple of years ago and I'm like, oh, you do Darknet Diaries. You should really interview me. And he checked me out and he's like, yeah, I really should. So, you know, different elements and aspects of the story have been telling the night would come out in the Darknet Diaries episode. Yeah, he's a really great, great guy. Andrew just asked a question. Does the cyber liability insurance run its own penetration testing teams? I'm not aware of any that do it directly, but they but a lot of times the insurance writers are very closely connected to other companies that do provide some level of assurance that the insure e if that's the right term, is insurable, and they would simply do it. But I mean, the first couple of years of the insurance cyber insurance industry was all questionnaires and and you know that was supposed to magically, you know, validate that you were worthy of the cyber insurance, especially if there was a claim file. So I don't think any of them do it directly, but they certainly because of claims against it and the need to. And I'm not an insurance expert, but actuarial tables, you know, figuring out how much you need to charge people that want to have this type of insurance based on how many claims are going to be filed and what's fair and all that kind of stuff. And the insurance companies can still make profit. They're starting to get more responsible. I mean, cyber insurance has been around for almost ten years and I remember being asked about it almost ten years ago, and I'm like, people are silly to think that they can skirt or dodge regulatory compliance by just getting cyber insurance. And in this context, it was PCI, because I'm like, have you ever tried to file acclaiming against an insurance company? You can be damn sure you're going to come back and say were You're doing all the things that you should be doing. So if you think the PCI assessment or audit was bad, wait till the cyber insurance adjuster comes out and looking under the hood. And a lot of times I think what they'll do is they'll hire like the forensics people to go in and say, well, they didn't do this in the insurance company. I'll have an easy out right, yeah, but I have heard of. I mean partnerships, I guess, or relationships where the insurance carriers do have relationships. I don't. Again, they don't do it themselves, but they probably have partner companies that will do a little tire kicking, a little bit of vetting of the people trying to get the policy to make sure that they're meeting some sort of minimal standard, similar to like, you know, I don't think insurance companies hire doctors. They don't have doctors on the payroll, but you have to get a physical to get a life insurance policy right most of the time, so that you know, they have partnerships and relationships or you know, you have to have the notarized signature of a doctor. I got to renew my driver's license, and I'm like, I can do it in the mail, right, except for I got to have the back of the form filled out by the eye doctors saying I can still see. Right. So the insurance companies will hire somebody that will put up CALI and say, yeah, okay, you know we ran port scans are fine yet whatever, But then if things go awry, the insurance company can also the claim can also be like ah, well you weren't meeting this thing. Yeah, it's very complicated there. There's certainly something to be said for, you know, some sort of minimum level of security, which is typically measured by some sort of compliance standard. Yeah, and and the cyber insurance companies are certainly getting smarter. But you you triggered. You triggered me a little bit because there's also this prevailing attitude in our world and in our industry that the ultimate test is a pen test, which, at some level, yeah, if you can afford it, that might be true, because that's rubber hits the road, live fire tests. Most companies don't want to pay for that, but they and I'm guilty of this. When I first came into the private sector, I started with, let's do what we called it a pen test, but it was really a vulnerability assessment. Let's see what you got, let's see what we have to work with. Let's see what your holes are, your vulnerabilities are, and let's start by closing them. I kind of thought that the industry would evolve, right, almost thirty years ago, God, that's almost thirty years ago. But you know, when I got back into this, you know, talking to Red Team and pen testing companies in the last ten years or so. I'm like, Wow, it's become this is what This is the ultimate test, and this is where you start. I mean, you should not start your journey of security with a pen test. That's the last thing you should do. Literally, that's the last thing you should do, because there's all sorts of more cost effective, economic ways to put security in place and test it and stop gaps and check it and the ultimate live fire test when you think you're ready for it and you're mature enough. Is a pen test A real test, not a not a vulnerability scan, not a nessa scan, not a you know somebody running a tool suite, this, that or the other, but you know, an actual You want people to try to come after you, and you're going to pay them to do it. Let them do it again, which is the methodology that was portrayed in the movie Sneakers, which came out in nineteen ninety two. Right, Jeff, thank you for spending your Monday evening with us and sharing all these It's almost Tuesday. I know we've kept you so long. We really appreciate it. We will be back on Friday with Jonah Mendez. Otherwise, Jeffy, any final thoughts, any final things you want to put out there before we get going tonight. There's no way to summarize this. Be diligent, be smart, be caring, and don't believe the vendor. And again, people can find you on Twitter at real Jeff Man to mister Jeff, mister Jeff on Twitter. You can find me on LinkedIn. Two f's one end and and the podcast one more time for everybody, please Paul Security Weekly. You can find us at simply securityweekly dot com. All right, well, thank you so much, Jeff, and we will see all you guys out there on Friday. All right, Hey, thanks for take letting indulging me with all this time. Absolutely, thank you, Jeff. We really appreciate your time. We had a question from Andrew. I'm gonna just ask you real quick, and this last question we're gonna take you. If I'm a fortune five hundred company, what is a pentest going to cost me? It's probably a percentage of your of your revenue. The presumption is a fortune five hundred company is a mature enterprise, and so you're going to pay more. But there's a lot of I mean, last time I looked nine out of the ten Fortune ten companies, ninety eight of the one hundred Fortune one hundred companies have to do PCI at least in some part. And PCI is notorious for taking a very minimal approach to pen testing, so it could cost you a lot, but it's very much dependent on what you want to get out of it. And if you want to do a PEN test, the first conversation you should have is what are the goals and the objectives? Because they are legion and you need to understand what you're asking for before you ask for it, and you should expect to pay accordingly. Most companies aren't ready for it, even in the Fortune five hundred. Frankly, I'd say maybe ten percent of the Fortune five hundred are really really mature enough ready for a PENT test, to really have a PENT test. Pen test being no holds barred. Can somebody get in by any means to do something? But again that's the goal or the objective. Are they trying to steal something? Are they trying to gain access to something? Are they trying to prove a point? Are they trying to you know, whatever it is? Xfiltrate data, lock the data. I mean, I don't know how many pen tests out there that that emulate a ransomware attack, right, I don't know. I'm gonna have to ask my friends. And I don't think you talk when you talk about like this full scope pen test, you're not just talking about hackers. You're talking or like the technical aspect, you talk about social engineering, you're talking about physical like Dvian Olam and those guys, You're talking about the entire gamut. Correct, Yeah, I mean, uh, And I apologize because you know, somewhere in the in the time that I took off from this industry, this term red teaming came about. What I call pendesting. Is is comprehensive, correct, But most people would call what I'm describing as a pentest these days a red team. It's Devian Olof By the way, that's how you pronounced that, Okay, I said, I said ol On for years, so we interviewed them, but it's all off. But yeah, I mean, uh, no, holds barred means somebody wants to go after you, uh, and they're going to do it by any any means possible. It's it's it's not simply now. The presumption was when the Internet came along that the path of least resistance, the easiest way rather than physically having to go to a place and try to break into it. Was like, oh, they're connected to the internet. Let's try to get in over the internet. But once defenses came came up in terms of the technology and the network perspective, you know, the physical type of thing was back on the table, and you know, the irony is it you if you really want to go after a particular company and you're motivated and you have resources, no holds barred means you'll try everything. There was a movie came out, I don't know in the two thousands, maybe Harrison Ford. It was called Firewall and the No spoilers, but the premise of the movie is Harrison Ford is like a firewall admin or a network admin at a bank and the bad guys kidnap his family and put guns to their heads and said, you know, give us the passwords, give us the UB key, give us the rs A key, you know, help us through the multi factor authentication log onto this firewall. That'll get us into the network, that'll get us to the safe to steal the money. Because we've got guns to your family's head. You know that's rather extreme, right, but but for motivated nation state bad guys that are really going after you, that's the measures that they'll go to. Most companies, you know, can't and shouldn't afford to pay for a simulation of that type of exercise, but you ought to kind of at least talk about it, you know, tabletop it. You know what would happen if somebody did X, Y or z. But not everybody needs to worry about that because most bad guys aren't going to do that because it's easier just to launch the ransomware attack or send out the phishing attack and just see who bite. And they're not targeting you specifically. They'll they'll just target whoever takes the bait. And if it happens to be a children's hospital and people die, you know that that's not what they're worried about. Right, problematic world? Right now? Do you have anything on Patreon? Okay, Jeff, thank you so much. We deeply, deeply appreciate your time. I appreciate you giving me the time in the audience, and yeah, feel free. Anybody that's listening to reach out to me. LinkedIn is probably the best way to find me. I do, honestly try to respond to people, happy to give back, happy to answer questions and mentor where I can, and check Jeff out on Paul's Security Weekly. It's p a u l s Security Weekly, correct, it is, But the website, if you go there, is just simply securityweekly dot com. All right, guys, you'll find us there. We will see you guys on Friday. Take care out there, all right. Thanks,