Hi, everyone. Very excited to have you here. Excited. Introduced Dr Andy Amoroso for the
see So security controls. Course 12 effective competencies
and, uh, take it away.
Okay, Thanks. Leave. Hi, everyone. Thanks for joining. What? What a nice
settle. Lectures. I hope we'll go through here with you. Um, I want I want to start with a story cup, couple of stories and then we'll kind of get into the course. The first stories that on Sunday mornings I watched the Sunday morning political shows. I just enjoy them,
you know, sort of middle of the road guy, but I enjoy them, and I know noticed that after meet the press.
Ah, Joel O'Steen has the show
where it starts right up, and he always says,
Gosh, I'd like to start with a funny story and he tells a joke and he gets into his thing and and you know, after you watch the show, it's on and I was listen
for a joke. Sometimes it's pretty good. So
I'm over shopping with my wife, or I should say, my wife is shopping. We're in New York City, and I'm standing there filling my phone
at one of these stores. Century 21 or something.
I'm filled with fear and I look across. I see some other woman like roughly three dresses next to my wife and her husband's there. And I look over and I went
my cuffs. That's Joel. Oh, Steve.
So I went over them and I said, Hey, do you do the guy on TV? And he started laughing and I said, You know what?
That thing where you say I was like to start with a joke. I said, That's like genius, cause that really does keep people on. He started laughing and said, That is the way you start.
Um, and And I would say something that really nothing do with cyber security. But when you start anything, whether it's a course, a seminar, whatever, always start with a story,
that that's the way you connect people in
to whatever you do. It's just gives him an idea that you're you know, you're going to be fun, and you're gonna keep it conversational on you.
You know, administrative E about courses is like the least interesting part of anything you ever do in your lecturing. People always start with that, and I think it's kind of a terrible way to start. Of course, let me give you a second story here.
When I was back at the Labs in the early days of my career, I wrote this firewall
Um, who's stolen over there? The labs?
reason we wrote the book is because
relevant and cheswick Steve Steve Bell that Bill Cheswick had written a firewall book and we were working 18 to building a firewall product.
And we noticed that none of our Castor's could understand Bill and Steve's book. Like at the In those days, there were people who barely understood the spiky. So we wrote a book that we thought help to explain their boat any right. I remember,
you know, because we were. We called it firewall strategies, and we wrote a little bit higher level. We dug into the
details of how firewalls work, but we also gave guidance on how you use it. I remember somebody looking at it and saying
so that's kind of like Maura management book,
and I remember being furious like you couldn't say something back at that portion of my career. That was more pejorative or more nasty or more vile than to suggest that I was a manager. It was like, What?
Management book? Are you kidding me? I remember. Pushed him back and sailing under protocols. We got code in here. Give me a break. Does not imagine because I was are arguing that you know. Please don't ever call me a manager. And God, don't ever call me an executive like that would be just about the worst thing you could imagine cause I always thought
in the beginning of my career that life was a bell curve
and your career was a bell curve, meaning the beginning of your career. You start up. You're kind of not so good. It's stuff. You get better, you get better, you rise up to the top of the bell curve and at the top of the current me or an individual contributor, you doing amazing work. You're making amazing contributions. Either is a developed
bird engineer a test or something that's an individual.
But then as you get promoted, you start moving down. That bell curve is sliding down the gun less effective and the worst thing you get interviews me like the CEO, then you're back to being is useless
as maybe when you started day one. That's how I always thought of careers.
I'll have to be honest
that there's still that bias with me,
but I know that it's not right now. I know it's not a hockey stick.
Like, you know, in the old days, you think of operations folks down on the floor and then you get promoted to supervisor him up a little bit, Then get promoted to director. Move up a little bit, then you're vice president. Move up a little bit, then you present your way up, perched above, looking down on the
factory floor like you just constant rise. I don't believe in that. I think it's something different. And for the people who are on this course, what I'm going to be sharing with you
are 12 basic principles
that I think will get you toward your definition of success in enterprise security. Now some of you let's say, Look, I want to be a VP. I want to be a C so and I'm gonna try and help you get there. There's there's no question that you make more money.
You have a lot of power.
People laugh at your jokes when they're not funny. You get to fly around in cool places. It's
there's some real parks to it, but there's also some disadvantages, and we'll get to some of those. But this really is a course for practitioners who are interested in advancing their career. Each of these confidences air around personal kind of capabilities or beliefs. Or
I think capability is the right sort of, uh, concept worker competency. These are the kinds of terms we're gonna go through 12
and each week we'll do one. We got a case study that's been sent out to you that I hope you're reading. We got I'll be bringing in some guests to share with you their personal nothing in each and each week I'll do a little lecture to take you through some of my thoughts on the on the topic on that particular competency.
Um, now, I thought it would be fun to do this
without any technical stuff,
so you're going to see each of the charts.
It's just some picture I took from somewhere
Well, and then a book suggestion,
like I thought that would be fun to do that. They had those dimensions that it's a course where I don't We're not gonna go through security architectures. I'm not gonna bore you with Power point list. There is not a single power point bullet list in here. I remember when Richard Feinman, my favorite person of all time,
um, physicist up, You know, the late, great physicist,
um, was testifying, you know, are serving on a board that
have been investigating the challenger accident Back in 80 against was 86 87 January 87.
And they were asking me about Professor Fine. Would you think of Washington Baba Ba And And he goes, you know, the one that you can't figure out our anytime soon. He's got to say something. They make this piece of paper with these little stupid round dots and they put around dot And then a couple of words, he goes, What are those goddamn dots and his left hand.
They realize he's talking about Power point bullet lists
and and I would ever see a bullet list. I think of those dots and crying and making fun of that so you could see any of that. This is gonna look a little different than things that you're used to sing.
So I hope you stick with us. I have a feeling you'll have fun with this.
That's how I always approach these courses. I've been teaching for 30 something years.
You know, I began teaching back night literally 1989. I'm literally that many years ago. It Stevens I talked linear algebra.
Um and I've not given up since. I've taught every semester the last 30 years, either Grads were undergrads. That teach a lot of these types, of course, is it's my great passion. And it's the first time through the material with Leaf in the cyber team, I think very highly of that group. They they said, Hey, let's do something. I said, Man, count me and let's do it.
And this is brand new. So as we go through it, if I say something you think is wrong, you gotta tell me because we'll fix it. This is the first time to the material. You guys air the inaugural class, and some of it's gonna be nice and smooth. Some of you, Bumpy, whatever. But you let me know and
and also with the book suggestions. If you think they're better books, you let me know.
But these are all books that I've read.
It was another thing. I wanna make sure these your books that I had something. So So let's start first off, I just want to show you,
that here's a picture of my friend Alex Stamos on and you could see that book there by Steven Levy. I'm guessing most of you have that book if you don't know where you've been. But, uh,
Alex is an example of the sea. So who comes from essentially a technical or hacker tribe?
And it's important because I'm guessing a bunch of you on this call would say, You come from that tribe. I sort of d'oh because I'm kind of little annoying Acker when I was younger and I come from that I come from a compliance back from that. If you were like that, then I think I sort of get you and I sort of understand
who you are in your tribe and what you're about.
But there's others like, here's my friend Tom Harrington, who was formerly the
chief security officer at Citigroup. I'm There's a book by Candace on their life in the F. B. I think I read that I'm obviously very big
supporter of the bureau,
but Tom comes from a different kind of background than Hacker Alex, but they're both were. Chief security Officer is both very effective. I'm going to guess some of you on this call come from maybe a law enforcement background, and it turns out I can count many different tribes. I don't like my friend. Gary McGraw
has written extensively on this this idea that there are tribes. Let me list off a few that I know, like some of you probably come from an I t R I. T. Operations background, right that there are a lot of people on this call
who would say I was an i t. I moved into security. That's fine. And that that's your legacy and that your experience base. I'll bet some of you came from
like a complete its background.
Maybe you were an auditor. Maybe your necessity, maybe this or that. Everyone consultant,
I'm and then you got into about bank or a place where you got more of an operational, something like the sort of like visionary si sos where you're
dance, the the discipline and you like the only vendors and you like looking at our whole industry And and then on on on, on on there's There's some people who, like a said commit, come from hacker or he might be a business person.
Maybe you were working in a business unit came over. One thing I can tell you
is that it's rare to find somebody who goes from cyber security to something different.
We'll get into that in a minute,
but recognize that when you do cybersecurity,
there's a very, very good chance that your CEO considers that you personally
are incompetent for any other job in the company. Maybe like in adjacent I t thing.
But what was the last time you heard about a C so moving to run the marketing team or run PR, run marketing and in some country or run operation somewhere or take over? The factories are
moving to finance. It does not happen, happens adjacent Lee. Sometimes to seek the security folk might might get promoted to run infrastructure where security is part of that. I've seen that,
but I don't think we as a group are viewed as competent for anything other than cyber security. We need to fix that.
And some of the learning here in this course will be geared toward making it more effective executive. So to recognize these different tribes. So so competency Number one for our course. And like I said, we've got 12 of these.
Is there an innovation
and innovation? Here's a definition that I wrote out. I'm going to read to you. It's as effective Seaside develops the habit of innovation. Not that just sort of the occasional use of innovation but habit,
which involves always seeking to do things in a new, wet new methods. Think if you're if you're obsessed with,
you know, do something new, let's navigate. This evolved to evolving threats. Seek new opportunities. Bump of other words of their new new, new, different, different, Different. That's innovation.
If you are that person who says, Well, this is the way we've done it. This is the way we always do it. Then you might be in the wrong line of business because if you if you want to be
an effective executive in cyber security and even if your definition of success is. I just like to be the head of our pen testing group.
If you're going to be a leader than you will have, this habit of innovation is you better.
Now let's set the stage for this. And here's a book.
A Madame Curie Look, Look at that picture. This was a solve a Congress Congress in 1927
Um, and by the way, just finished Walter Isaacson's biography of Einstein. Man, if you haven't read that,
it is amazing. Einstein was a weird dude, man. He's not the greatest guy, frankly, but what a genius. A fun read.
But I came out with it, maybe not thinking as positively about on since as I had going in. Nevertheless,
there's Madame Curie, and there's all these great businesses. Look at the names. It's like all the constance you that you used in high school college physics, right?
But the point is, from about 18 19 about 1930
the people in this picture change the world.
I mean, change the world changed the nature of how we look at things change the nature of how we, you know, do engineering. I mean, every everything we do in computing now is made available because these people, But what happened in the thirties? Everybody freaked out because we realized, Wow, this innovation has good impact. Meaning,
you know, we can go do electricity and then an electrifying rural areas. We can build semiconductors eventually. You know, we got to that the forties with the Bell Labs group, and I'm another night, All these wonderful things. But
we also couldn't build nuclear bombs, atomic
atomic bombs with a frightening concept.
And, you know, you see Einstein there He was persuaded by Edward Teller
to get a letter to President Roosevelt demanding that he pay attention to this and put some effort into it. And thankfully, you know, Hitler was just idiotic enough to to push these great German scientists like Einstein out. Thank God they're working for the good guys. And it helped change history. So
I think we would all agree if you're gonna do physics, Man, this was the time being at that meeting right there. I was getting like people, you know? You play those games we go, man, if you could be anywhere talked to anyone or transposed, what would it be? I would say I'd like to be at the soul mate in 1927 like sitting between
you know, Einstein and Lawrence was
who was his hero. You see the red sitting there next to Einstein with legs crossed that he was an older man, but Einstein had more respect for him than anybody else in that picture. And there's some really smart people. There's high Heisenberg, not the
not the one played on the TV cooking up meth. But that's that's the realizing bird. So here's the point.
40 years of amazing innovation, followed by Whoa, you can do good, but while you can do bad now let's go look at this guy.
that the word suffer engineering was first cooked up. My dad was at the conference, was a kind of NATO conference, and it was called Suffer Engineering. First time that had been used
Count forward 40 years from 1968 and you get this guy
that those 40 years changed the world as much as as those previous 40 from those physicists, right This is pretty astounding change in our world from late sixties to now and computing. Are you kidding me? And I would say, if you want to do computer, that is probably the best
time to do it. I'm sorry if you're just getting into it now, it's still awesome thing to do.
Just like physics is still awesome. But, man, those 40 years were amazing. Then what happened to live the first and second decade? After that,
we all realized, Oh my God, that's amazing things we could do with computing now, including artificial intelligence having its rial, you know, second coming. You know, we're gonna actually do things with it. But also, there's some scary things that you can do,
and it's called hacking. It was called critical infrastructure attacks, and it's called weapons of mass computing destruction.
And I wrote a letter to President Trump. I'm pretty sure got their, you know, basically warning the same thing. So so recognize that the backdrop when I say innovation, what I mean is,
sensibly providing protection for things that are changing so fast
that it's hard to keep up.
that you can put a cybersecurity program in place without the ability to be nimble and open to change and always challenging yourself to do something different.
Then forget you're in the wrong business. Go do something else. No. Go sell coconuts for a living. If you can't do this, think different. You're in the wrong business. I have. I wouldn't spend a bunch of money. I don't spend money. My wife always thinks I'm just like crazy. I would never buy anything.
But I saw the original Apple poster
for that. Their ad that said Think different. It was basically was Buzz Armstrong on the on the surface of the Moon.
And it just says, Think different was original poster and, like 300 bucks.
And I said, Oh my God, I have to have that That's hanging behind my desk
And every time I walk to my desk, I see the word think different and it reminds me
that the business were in the discipline we've chosen. The people on this call chosen
demands that you think different and let me give you a cool example.
there was a prize fight. It was Holyfield Riddick Bowe Now
some of you may find fighting to be pretty miserable. Two people pounding each other's heads in my wife. If she even sees me go near watching something like this on TV, she gets annoyed, barbaric, and she's probably right.
But I guess I grew up in a time when I sort of liked it. I was watch Mohammed Ali and
Joe Frazier enjoyed it, but whatever. But at any rate,
people would pay big money back in the nineties. I think they still do. I don't now. I don't know the heavyweight chances right now, but
the doctor 90 choose big deal and this picture on the right. If you share generation with me, you remember looking at that.
That's where you didn't pay for the channels that were. You know, in some sense
they're scrambled, wasn't encryption and they were scrambled for a reason, because you kind of make out figures. Unlike the naked channels and stuff, they would do a bad job of scrambling.
So if you were about 16 and it wasn't scrambled, man, you wanted that channel because you see that it just sounds ridiculous. But that's just let's craziness of the time
so That's the scrambling that you would see if you hadn't paid for the Holyfield. Both fight. Now, here's the bottom on
in those days, set top boxes were not tamper proof.
So what you could do is you could take the top of the the set top box off and look at circuit board.
Not that I did this, but maybe I did.
And you take the top off me. Look, you know, you're looking all these chips and connections and stuff. You look for the CPU, and even if you're dumb, you figure out what CPU is like the coolest, best chip on there.
You look it up in. There wasn't really much of a World Wide Web there, but there was an Internet. You could look stuff up
and and I remember those days you'd go to these T TL websites or places or
1 800 numbers were with a catalogue.
And if you found the CPU on the circuit board for your set top box,
you could look up that chip from its manufacturer and you would find that they sell the same chip, that same number with a capital T after it, which meant
it was the test ship
that comes to you in the mail. Lupin cushion! You pop it out of the pin cushion.
You take the chip off the circuit board. A lot of times they even have a dip. Sauder on the corners. If they did, you had to have a sada ring. I need to eat it up to pull it up. Whatever. Minor, minor speed bump for a hacker. But you're pulling up. You put the test chip in, and suddenly you get all the channels,
everything you get. You get to see the whole kitten caboodle
channels, which causes a problem. Now, suddenly
you've got people who were ripping you off, who were stealing the not paying
and they're getting the fight. They get all the channels. So there was a cable company
in Connecticut that I remember in those days we have had some interaction with them.
I didn't think this up, but I really we're finding out about it. Just I think we're getting contacted. This is like the coolest thing ever heard of. But here's what I only read it to you.
It's a Continental Cablevision of Hartford, Connecticut broadcast a special offer of a free T shirt during last fall's Bo. Let me show you a picture. Then we'll come back to this. You see the thing down here just to receive your free T shirt, please contact us at now. You see, there's the fight, which means that this is what you were supposed to see.
You hacked the set top box. So you see this You follow. But now what they did was
they created a special offer, a free T shirt,
and said, unlike most pay per view broadcasting,
this one did not show up through legitimate decoders. They decoded it,
so if you were legit, you'd see gobbledygook here. But whatever, it's not gonna bother. You can still see these guys beating each other's heads in. But you see gobbledygook there.
So this you didn't see that you backed the set top box. You're gonna see gobbledygook here because they created that. And then what they did was the ad and it showed up with an 800 number
and they said, Hey, you know, call us and we'll give you a free T shirt.
And 100 and 40 people called the number
just within minutes of it coming in
and they sent the T shirts and they also sent a follow up letter saying, You're ripping us off and you need past $2000.
Um, and here's an article in Chicago Tribune about that. How freaking cool is that, right? I mean, this is not a firewall.
This is not public. He cryptography,
This is not two factor authentication.
This is really innovative cyber security operations. In my mind, this is some seriously cool stuff.
we have to adopt a couple more shakers of this in what we did. E mean, the problem that we have. Ah, let's talk about this for a minute. I think this is This deserves a little bit of discussion here
in our business. When you do cyber security,
you're taught that there's the set of controls and and and I contribute to this in some degree, a swell
where we say, you know what? Um here the controls that matter
Father's governance. So you need to be doing governance, risk and compliance. We need to have a whole program of
making sure that your compliance controls are in order and that your team has the documentation in place and lovable.
And then we tell you that there are these endpoint control. So you need to have
I need to have something on the end points that you know, the state of collection
and detection and response. Maybe does some other types of analytic functions and protective functions that that stop certain types of attacks? And you could argue
that the end point, you know, the set top box here Had it been maybe not tamper proof by members that have been tamper proof. Like when you take the top off. If it could have broken, maybe you could have prevented this sort of thing. But setting that aside way focus on these controls. 1/3 type of control would be
maybe network at the network level.
We tell you, monitor network activity, you collect data and you process it. You, you know, send the alarms off to, um,
some SIM person processing engine to do the detection. And you know the nana that these are the tools in our tool kit. These are the things that in our mind
makeup, cybersecurity, if we play word association is a cyber security architecture against a firewall. The emcee Cloud. And like all these types of things that in some sense someone else has dictated as the categories of the tool kit that we have at our disposal. You've all heard the story that if you've got a hammer
and a screwdriver in your in your toolbox
and you're going to do some task than everything is going to look like an alum, screw
we will need to de program ourselves from that. I really believe that. And I contribute a little bit too. This tag cyber in my company, I published 50 controls. I published market reports in these things and comment on the effectiveness of all these different controls vendor solutions and so on, kind of reinforcing that these are the tools of our trade.
One of things you're gonna hear from me
is that we need to be a little bit more obsessed with this idea
that you know what? Come on, man.
I don't need an intrusion detection system from a commercial vendor to detect intrusions. What's with the look what these guys did. Look how cool this is, Man.
I think this is about his cool thing is your
you're ever gonna find this idea that you're using
There's really no vendor here.
You invented this. You thought it up. You put a whole scheme in place. You caught
malicious actors. You demand that a fine probably required, covered quite a bit of money, freaked out a lot of people. You reinforce the tamper proof issue You. There's just so many cool things that come to mind around this. But maybe the most important is that allows us to look at ourselves in a different light. Let me give you an example
def com. I don't want to say Black Cat. I want to say, Def Con,
you know what that conferences like right? And I was feel very self conscious because I don't look like a deaf Connor and I've presented there a couple of times, and it's like,
you know, that nobody's really in charge and you're
and I was wear khakis and a chambray shirt or something. I would look like a hacker. I look more like the accountant, look like the guy works at the hotel, you know where they're having the conference, and it just feels weird But
what I love about that whole environment is a celebration of technology. It's people being themselves, having fun,
breaking into stuff, sharing, laughing, being a little snarky, just really doing what in many cases is what they would be doing. If they really couldn't make another penny the rest of their life. That just wouldn't do it. Any way to culture, to celebration of hacking, and I get a lot of credit.
I don't always agree
with some of the things that get published. I'm not a big fan,
you know, for example, hacking live, you know, minivans, you know, on highways where there's real people driving rings responsible. I mean, there's a lot of irresponsible stuff
that goes out in the offensive community. But that said,
it is a fun celebration where they don't talk about buying vendor tools to talk about doing stuff,
trying things, being creative, being innovative, that is, if you had to use a word to describe those places, these hacker conferences and hacker groups, and maybe go to B sides or other than since all that innovation now, transport yourself
to the gardener summit.
Just close your eyes and walk in. What does it look like
that? Boring. We're all boring people. We're grown ups Were jacket over, pants were male or female. We're not smiling. Would rather not be there. We want to go home. You're going to go to a talk at one o'clock about compliance controls for
now, the GPR and you know, you figure while it's boring, I'll do my email. You just want to be there and it zal this. You get the point.
It's not fun. That's not innovation, that being locked into a bunch of different things. In fact, compliance does that to us.
It drives us to a mindset where
you don't want to change anything because you're going through the compliance process, like less than you want to do is redo the documentation, right? I mean, suppose you had very specific controls, that you swore to some Ah, like a regulatory group that any time you put something on the screen here, it had to be regulated.
Look, you wouldn't be able to do this
because there would be a control that would prevent you from being innovative. So the point is,
which is more fun Def Con or the gardener thing? I think def. Con is way more fun,
I think we got to somehow get out of that. We got to get to the point where it's just a CZ much fun to play defense as it is to play offense. If you coach high school sports, if you coach
football, for example, and
you know you got kids that all show up, the one kid wants to be a linebacker and another kid wants to be a running back. You don't say to the running back. I am gonna have fun. You're playing offense and then you play. You say to the defender, The guy was played line linebacker, although is going, you're gonna be pretty bored back here. But yeah, go for it. It's ridiculous that both is just as much fun,
and we need to figure out how to adjust that mindset. Let me go one step further.
the defense of work that we do requires 10 times more innovation.
I've run a lot of catch the flag type things. We think one recently N. Y U where I teach,
um, along with the city of New York, your school thing
and I remember we had a bunch of reporters in
and they all came. And you know, we're all standing in the room where the
the you know with a defense was all situated is most N. Y. U students and a bunch of New York City
employees, and they're all sitting at the consoles of the platform we were using. You know, when you do those capture the flag to engage with commercial platform, they train everybody. And what to do is a bunch of files, and the offense has to make their way in and steal files or change things or whatever the engagement's about you. You're all familiar with that.
Remember, we're all in there, and there must have been
40 or 50 of the kids and New York City employees on a room.
No school. We're going around and they're being interviewed positive feeling. And they're showing us, Yeah, they're the offense in the other room is breaking in and they're kind of even. You know, we're stopping some stuff. They're getting into some stuff. It is what it is. So then all the reporters want to see the offensive team,
so we all wander down the whole way. But but But but But we get down, you know, where was leading
tour saying some stuff. And then we look in the window and there's like, Bill sitting there
and that's the offense.
It's not 50 peoples. One guy, they were rotate E. It's It's like one on 50 is considered a fair fight.
Nobody said anything. I was sitting there squirming begets a reporter's gonna go. What gives here, man. One on 15 minute break cycle that school year. There's the hacker, and there's the 50 people in the way, about the same. This is utterly ridiculous.
So who needs to be innovating? War? Give me a break, man. It's easy to do offense. It's not easy to do defense. So look, when I said at the beginning,
you want to get ahead here. Then, for God's sake, developed a habit of innovation. You've got to be trying stuff
now. There's a downside.
And here's the downside that Henry Petroski, by the way, right school books, does my favorite of his engineers human.
And that's the Tacoma. I think that's the Tacoma Bridge, right? The one that gets residence
the downside of innovations you could break stuff
and you can cause embarrassing situations and you can create problems and you can create issues and you can cause outages and you can cause embarrassment. You can cause misunderstanding. Welcome to innovation. Innovation is not safe.
If it's safe, then you're not feeling it right. Innovation means trying different things. And when you try different things, that means they're not tested, which means some are gonna break.
So look, I know that Comma Bridge maybe wasn't all about innovations, more about engineering failure. But I love the idea of this this Petrovsky book of sea So is taking the time to really understand that subtitle in that book.
And it's called The Role of Failure in successful design.
Here's the problem. Go back. If there were done, take out a pencil and paper and write down your 10 biggest failures in your career
on and then trace back. You know what happened after that?
Did you become a better engineer? Tester, developer, manager?
Where did you become worse as a result of that failure, I bet you became better, and I'll bet whatever you were working on turned out to be better because of that failure.
So this is the tricky part. You might work for someone who may not agree with this
and years of stupid ed on this, you know, cyber everything, telling me I'll go innovate. Well, he doesn't know the lady I work for, man. She's not gonna let me innovate. I work in a box and forget it ain't gonna happen. We don't know what to tell you. I mean, you should at least understand your constraints if that's the world we live in.
Um, I wish you didn't. I think you should look for another job. If you can't, then you deal with it. Life is life. I mean things. They're not perfect.
But I'm not gonna lie to you
if you cannot innovate if you work in a box. If everything you do is dictated by some compliance manager
or by someone who's determined around you
what you're going to do and you need to live with those horse blinders on,
you're never gonna get any better, Period.
You should least understand that.
And if you can deal with it that you do with it. But but But this is a tricky one. And let me say a couple more things about fairy before we get into
talking about our case studies. So I want to spend
leave us a good 15 20 minutes to get into the case study and sort of frame for you.
But this piece is something like if there's one thing that you take back, maybe to your team
for a discussions, love you, you know, working in work groups and you'll want to go back during your
your weekly or monthly meetings with your team, and some of you ought to bring up some of the topics that we cover in the scores.
I think this is a good one to bring up this debate between
as a group. Does it make sense
dressed to willingly acknowledge that if we try some things differently
that were likely to break some glass? Is that except
And if it is, then what is the process for selecting
where we innovate, where we don't? That's something that's gonna be case by case. You need to look at the environment where you were.
I need to determine you know what sort of the
what's the local culture where I started in my career. I worked in a laboratory
where you had a long tradition of failure and Bell Labs, but had a long tradition of successes that came from things that looked like failures to just dump the UMP. Different cases made many of right now
are watching this, these charts
on a computer that has UNIX at its base. In fact, all of you do
because I know posits is part of Windows. So and obviously UNIX is embedded in Mac OS, and it's embedded in your iPhone and your android. So that UNIX operating system,
Where'd that come from?
Well, Dennis, Richie and Can Compton and some others that I had the great privilege to meet a little bit of work within the latter portion of my career.
They were working a project that was called Multex
in the mid sixties. So think
Lyndon Johnson is president.
I dream of Jeannie is probably the show you watch on TV.
Uh, if you wanted the coolest car, you goodbye Mustang.
You know, there was no Internet wasn't even touch tone telephones. That was rotary telephony.
So, um, it's that there's this project
where it looked a little bit complicated. Daniel, Bob Rowe and other people were working on this thing
and the Bell Labs guys looked at it and said
Is that this is gonna fail? It's just too complicated. It is not right Something not right about this.
So I went back to work and they took Multex and they simplified it to something they called
That's that was the the Genesis, and they simplified the concept to let's see if we could just improve the text processing for a secretary. It's really one of you. If I could talk to this guy. I mean, the ones that are still around.
Um no. Brian Kernaghan and others. He's over Princeton. I had him is the speaker by conference two years ago, so, so much fun having income.
But if you talk to them very modest
kind of goals. But it all came from what arguably was a failed project. And Multex, you don't talk much about Multex. Now.
You talk about UNIX because they took the failure
and they created a successful design.
So when did you when in your career have you had that? And welcome to cyber security, one of our great dilemmas. *** it! We're not allowed to do that.
You know not to fail here, See? So you fail, you're fired.
But I say at the beginning, you're viewed is basically being incompetent for any other job in the company.
So you get to keep the job the instant you fail, you're out.
How crazy is this ***?
Because it forces you If you want to keep the job,
do not take any rest.
And welcome to one of the reasons we all get hot.
You got a bunch of sea so sitting in positions, looking over their shoulder, worried they're going to get that getting fired If they try anything new, doesn't work out. They can hack doesn't work out, You know you're out.
You can't try things that are new
because you're afraid of risk. You're afraid you're gonna fail. Your viewed is incompetent for any other job in the company. And you can see the dilemma here is that makes sense. I hope this is all clicking for some of you. A lot of you probably have never felt what it feels to be in that executive role, and that's what it's like.
Part of the problem is that *** C says get paid too much money.
And once you get started paid that money,
then you don't want to stop.
You want to keep the money, be better if we put a cap on what's he says make
so that they quit the sea so roll they could go into it and incident response role are
Cloud developer whatever make the same amount? They probably have much better. See says, if you weren't paid the amount of money
that we pay to get the pieces into the role, but that's another discussion.
So this issue of failure and successful design is absolutely essential for you. Have an opinion about Go back and talk to your team about it. Now
you have been mailed a A case study. I want to talk to you about him. Use the remaining time to talk about this.
I sat down and I created this
this scenario with a woman name Emily, who's a security executive.
I have her in front of a small group of CEOs giving a little talk under Chatham House rules, and I thought it would be fun to just have 12 little little big nets that just sort of lay out a situation
that allows us to have a discussion.
And in each of the sessions here I'll spend about five or 10 minutes on these and then we'll have a guest. They didn't want to bring a guest in today because I wanted to just introduce you to the course, and I'll have a little bit more to say about the administration in a minute. I was like, Dude at the end,
But we'll do a little bit of case study each week. And then on Tuesdays
at one o'clock in six o'clock, P. M. Eastern
there will be you've already received the calendar invites to join discussion sessions around the case studies this allow you with up. We've got two wonderful T A's
that have been doing this once. I bury for some time there listening room. Right now, you'll meet your T A's, and then they're gonna organize some discussions. I strongly encourage you to join.
You know, one or more all of these sessions. I think you'll like them
and you'll have the opportunity to go through the discussion item. So let me
let me give you an idea of how these things work. I'll take you through sort of the story here. I'm gonna tell you the story without reading it. That's done. You could read it, but I'll tell you where it came from. What I was thinking here, I had the idea that
many cases we like to try new types of controls really would like to.
And I remember when behavior Analytics really was no
today, you'd call it a commercial.
You be a or you'II be a tool. That was wonderful. Companies that do this, you know, observe it in others really good cos cure Onyx does something,
you know, there are many more jazz networks has nice tool. You have a lot of really good options. But in the early days you did.
We don't really know how this works. This idea that let's drop something onto a computer
that kind of sort of observes what you're doing
and then provide some, uh,
you know, some telemetry back to a station where I can go in.
You know, there's almost voyeuristic kind of experience of seeing what the behavioral activity is on an end point.
Um, and I was a little icky about it. I wasn't quite sure what was made sense. My my mind. I was thought
controlled environment. Like a call center.
It seems perfectly reasonable, cause the expectation we sit down, strap a headset on and you start taking customer calls from a PC
is that you're in an Arab. You're on a headset on your
asking for last four digits of social. You're asking to confirm zip code. You're making an account change. You're asking if there's anything else I can help you with. They say no. You say thanks for coming to Acme. 123 bank. I'll see you later. You hang up, you go to the next customer,
that PC? The idea that you would be policing activity on That seems perfectly reasonable.
And most workers would be okay with that. You know, they're not going to use the PC to go buy *** on Amazon.
you're a developer. You know, you're working the finance team and you walk around with your laptop
That I'm not sure. So I remember it was kind of unclear in the early days, but there was some pretty innovative groups that decided, man, we're gonna try this and see what happens
so I created the story where Emily, our hero,
is working with a member of her team. The analyst says, Hey, I'd like you to try this very innovative
new control like the Deploy it and what it does is it monitors our employees and Emily goes, uh, we mean you no behavioral tool kit.
I made it from researchers at N Y U There
you said you will drop it onto species and Emily thinks of that. And she goes, Boom,
seems a little weird. I guess it's okay. It's innovative, certainly.
And she even reminds her, says, Look, you said We need to be innovative. This is innovative. Let's try it.
So she goes back. Emily goes back and talks to the senior leaders and says, Look, we're gonna try this, but I swear, promise
we're not gonna run it on the senior executive
peces. And some of you are probably laughing. If you work in information security,
you know that it's harder to do
security for three desktops in your company. The CFO, the CEO in your CEO, then the entire rest of the company, right? That's more a lot of times you make the bad decision to put no controls on those things. No monitoring. Leave him alone. The last thing I need is a problem CEO,
and it's a shame, because there's a lot of risk there. But nevertheless, Emily tells this person, Okay, that's great. Do it.
But I've told the senior leadership team
that we're not going to
be running this stuff on their PC. And they all joked about like the joke was significant enough that everybody noticed it
when she brought it up.
So week goes by and some team members come back, and I have them sort of looking like they'd seen a ghost. One of says, Um, our C F O.
Looks like he's a total creep.
Inappropriate downloads. I put stuff like he's looking at cheerleader stuff, and you wanted to be
like illegal if it's illegally called the FBI.
But if it's just a little weird, you know, like huh
had certainly against the company policy. So there's no question that this is a policy issue,
but what sort of on the edges not really illegal? I if you quibble with the
example, I ever put your own example and try to think of something. I tried hard to think of an example where you look at it's creepy and weird, but it's not illegal. That was the idea of trying to come up with that.
But someday come back and I go. It's creeping were not illegal. What do we d'oh
and Emily go? Uh, great,
because she's told the leadership team she's not running it on their computers.
But what happened was they did it by see if they did it by accident. They said,
You know, they've been making my bubble bond, she says. Well, I told you, you didn't do this to go on. We made a mistake.
We went in with deployed. Everything it was someone made a mistake and deployed the tool everywhere, and I didn't realize this at first. That's what I wrote in there.
So Emily's like Mom,
Um, what should I do?
And that's where the three dots for months, you. She then paused for effect
and lead toward the group. Here is exactly what I decided to do. Dot, dot, dot
and not you now. So welcome to Emily's dilemma.
So this is the kind of thing that we will do each week. We'll do a little case study like this, and if we were all together right now, I'd say, What do you think if one of you would say Come on in, It's piece cake
You just go to the CEO and se R C A phone's a creek firearm,
but recognize that you've just been in there a week earlier and swore that you were deploying the thing to their computers
so they might say, Yeah, you're right. But also, you don't seem to know how to deploy software.
You must be pretty incompetent here. You said You're not pushing it through our computers. You know, howto restrict that.
Maybe Emily loses her job here like this. She get fired. Is that possibility? It could be
another one? Is that Emily says, Look, it's not illegal.
It's a little weird.
One of we just I don't need this problem. We've got other things to d'oh.
I'm just uninstalled from their PCs, and what I'll do is I'll reinforce to the leadership team.
You're some awareness training
that hey, as a group, I just want to remind you all
that, you know, looking at weird, you know, websites of cheerleaders and stuff is completely off the charts inappropriate.
you know, if you're doing that,
then cut it out. You know, without having any names. Remember, you're making it clear and you keep the stuff running on the PC. Maybe in your watch. And if the behavior stops, then you stop the behavior. Maybe that's what you d'oh or something else. You get the point
like, welcome to the executive ranks. What do you do here? And I don't think there's a right or wrong answer, right? I mean, I think in both of the cases, I just cited one where you have just go in and fess up. A lot of you would want to say that, but suppose you got three kids in college
and you got lots of bills and you need the job and you just move there. You just took this job. He loved the family there.
And you really want to take root there? Do you enjoy it? And you think I really do want a comma causing my whole career over this? See, if I was probably not gonna get fired anyway, why don't I just do the train? So that's one. And like said the other one where you just look the other way? I I don't know yet. The point
You get the point now. Number five here. You could say could she lie
and explained that it was a proxy review that caught the CFO and not the u E. B. A trial. There's an example. Something I hope
that you wouldn't do. I was trying include a couple
of possibilities in the discussion items that I would consider to be personally,
um, pretty unacceptable. So, you know, maybe the word lie is the giveaway there, Um,
perhaps our t A's might. You know, dr those things up again, because maybe we didn't call it lie. And you ran a proxy review. You saw it?
Well, you say, how did you find out about this? We saw in the proxies? Yeah, you did. You not be telling the truth that your first saw it in the U. B A.
That may be started blab about you get the got the idea, and then ultimately,
every one of these case studies
closes with more or less the same question. What would you do?
You know, if this is you, what would you d'oh!
And and and I really do think it's important
for you to develop an inner voice. Here is a sea. So now that's an interesting point from a technology perspective, because
we all know that at some point, like it or not,
um, artificial intelligence could give us the right answer here, right? I mean, look, we we take all of our experiences. We take courses like this, we try to learn, we try and become better informed so that we can make better decisions.
Well, you know, Google has taught us that if you take all the possible information, probably the best decision of all. So I would save you, Fed every possible case study into a piece of a I in the future.
The answer here becomes very deterministic. You know, the probability is that
your best case would be to go talk to the CEO, tell the truth, take your take your lumps, and in the long run, you turn out better for that. You know, maybe that's the rational answer, and it's a deterministic thing. But until we have that, you personally still have to listen to your inner voice.
You can't google the answer here. Our grandchildren, maybe they catched, But you can't. You still have toe. Use your judgment. You still have to
become someone who has the right sort of understanding and judgment around this and notice the case study here on innovation Tried to reinforce the point that
you're trying something new and you might decide well, the right answer year
is right back to the topic that we started with.
We're innovating. We're trying something new. You go to the CEO and say, you know something?
This is brand new stuff where it's cutting edge.
Maybe I were clear he wasn't clear enough when I first said we were gonna try and do this. But this is new, different, innovative stuff and maybe didn't work perfectly, But we're not gonna stop taking risks. And look, we found something and I'm sorry. It's not my fault that the CFO is a creep.
So this is what we find. And as long as I'm in this job, I'm going to continue innovating. And I think you'd be crazy to move someone else. And you know, Bob above about
innovation in this case is the point not around judgments. Right in When you innovate, you break just like I showed you here.
The role of failure and successful design.
This is all about the role of failure and successful design. They're going to go in, read, rethink how they deploy,
tune it up a little bit,
get it just right, and boom, run you B A is probably a very effective control in their environment,
but they had to fail a little bit in the beginning. You get the point. You see what I mean? So
so that really is the cadence that will be following,
you know, through our 12 lectures here, I hope you stay with us. I mean, I think you're going to enjoy it on if if you don't, Then
let me know if you think there since I could do to make it more enjoyable for you.
I know how valuable an hour of your time is.
And and I also always try to finish, you know, within the hour, even a couple minutes early. Like I've learned a long time ago
that you start going over and people started getting a little fidgety. Um, I like to make sure I give you a couple of minutes if I can before,
Before the time is up, but I hope you stay with us. We'll go through the 12 pieces and those of you have interest in the actual charts here.
The cyber. The folks would be happy to make them available. I just don't want to show you the new ones because you can see it's fun to see the reveal. You know what I mean? Like after we do the lecture,
Um, you know, a little webinar lectures here. You can get you to the structure side. Very happy to give them to. Um I'd ask that you not post them on Web sites and put him around on Lee because it'll ruin it for the people. Take. Of course, next time I think they're fun to see. But if you find them useful like these, this this little story here Holyfield bo the scramble
chur what they did and then how they entice. That's a cool picture and a cool story to tell Now, if you like that, you know, by all means use the charts. And by the way, I hope you read these books.
Petrovsky Book By all means.
Definitely. You haven't read the Steve Jobs Book that again. Isaacson's one of my favorite biographers,
Madame Curie and and these two books that Steven leave You had the pleasure to meet some number of years ago. I talked to a few times. And then there's a lot of good books on the FBI, so So go back and take a look. You know, order those books on Amazon. There will be enjoyable reading and
and unfortunately, you're going to get about 60 book recommendations through the 12 lectures. So I don't know if you can read 60 books, but I hope you read some of them. So So look, we're at just a few minutes before
Get on a welcome you to the course.
I hope we see a lot of you. Ah, at our next lecture and and my email address, which I put right up at the front here
E Amoroso tagged as cyber dot com. You're welcome to drop me a line if you want to. Tosto publish something directly, probably Justus. Well, that you work through the cyber team, you can get notes to me, but
let's keep a dialogue going and hopefully we'll have a really wonderful session together.
So with that I think there may be. Look and see if we have any sort of
and click on the chat here.
Um, I don't think we have any chat comments, but what we'll do is we'll work out a cadence with all of you. Um,
moving forward. Yeah. There's a lot of Chet. Let's see. Um,
mentioned you again, but that me the interviews. Yeah. We're definitely gonna be talking interviews that we looked through. We have definitely have a surprise guest next week. Slide desk available. I think I dressed most of these.
yeah, we do have guest lectures. They're not guest lectures, but I'll have Panelists that come in and I'll interview them about their career. So I think I have a lot of this going. Apologized my bed. I didn't really have the West does the chat going here. I see a lot of
interesting things that are coming in here. Let me make sure I've addressed everybody.
I think we got most of this. Looks like you guys were having a little discussion jet. That's perfectly fine. That's good. I'll make sure you keep this up
during this. Um, I think I got everything.
Oh, yeah. most of us we've got in here. So? So by all means, have the chat during the discussion next week, I'll keep it up. And if you really need my attention while I'm going through this, just we'll come up with some cadence, put some little head Stop what you're talking about an address this now, and I'll try my best to do so. So again.
Tuesday's 1 to 6. You've already got the invite. That'll be out.
Do anything for you to speak
to be part of the group to have the discussion about the case study and my email IHSAA veil open and available. If you need to send me something, Private
leaf, I'm gonna turn it back to you. I don't know if you have any announcements for the group or anything you wanted to share before we close.
Uh, thanks so much, and I really enjoyed it, Especially the story about
the Riddick Bowe Holyfield fight. Uh, amazing innovation opportunity.
Uh, just a reminder that next week, same time we'll be going through the administration side. So really looking forward to that. Um, and
there will be a surprise guest, So looking forward to seeing everyone again.
Okay, We'll see you later. Thank you. Everyone