Each time Jim links to Newsbreak the website and gimmick looks totally
different.

Last time it was a fake news style reprint of a real news chinese
national article, I think.

This time it just gave me a link to what it claimed was the
publisher's article without any text, but I had to enable javascript
for the link to work. Turns out it's a videocast that plays in a
site-specific player.

I found the same episode at https://vid.puffyan.us/watch?v=33aXMgId2CU
(an invidious instance i.e. youtube frontend). Different publisher.

I haven't reviewed the video but it seems focused on QuSecure which is
maybe some kind of hosted quantum technology provider, and doesn't
have a strong presence on google news. Subtitles attached.
WEBVTT
Kind: captions
Language: en

00:00:00.020 --> 00:00:05.960
[Music]

00:00:05.960 --> 00:00:07.600
hi I'm Jeff rankie editorial director of

00:00:07.600 --> 00:00:10.000
manufacturing.net and Manufacturing bus

00:00:10.000 --> 00:00:12.880
technology welcome to security breach

00:00:12.880 --> 00:00:14.360
this is usually where I dive into some

00:00:14.360 --> 00:00:16.560
recent attacks or stats to help set up

00:00:16.560 --> 00:00:18.080
the topic that our guest for the episode

00:00:18.080 --> 00:00:20.080
will be covering I'm going to deviate

00:00:20.080 --> 00:00:21.480
from this today because when it comes to

00:00:21.480 --> 00:00:23.119
the issues surrounding Quantum Computing

00:00:23.119 --> 00:00:24.720
and the impact on Industrial cyber

00:00:24.720 --> 00:00:26.560
security I think it's better to Simply

00:00:26.560 --> 00:00:29.160
get right into the conversation however

00:00:29.160 --> 00:00:30.599
before we do that we're excited to

00:00:30.599 --> 00:00:31.960
announce that security breach is being

00:00:31.960 --> 00:00:34.200
sponsored by Penta for more information

00:00:34.200 --> 00:00:36.160
on how automated security validation can

00:00:36.160 --> 00:00:38.079
help you safely test all your it

00:00:38.079 --> 00:00:39.640
security controls with a click of a

00:00:39.640 --> 00:00:41.600
button in a Non-Stop industrial

00:00:41.600 --> 00:00:43.960
operational environment visit

00:00:43.960 --> 00:00:46.199
pant. it's now my pleasure to introduce

00:00:46.199 --> 00:00:49.360
Skip szeri and Paul fugner from ccure

00:00:49.360 --> 00:00:51.199
skip is the company's co-founder and

00:00:51.199 --> 00:00:52.960
Paul serves as the Director of corporate

00:00:52.960 --> 00:00:55.239
Communications Skip and Paul thanks for

00:00:55.239 --> 00:00:57.879
joining us today and welcome to security

00:00:57.879 --> 00:01:00.079
breach starting right at the beginning

00:01:00.079 --> 00:01:01.199
you know I noticed something on the

00:01:01.199 --> 00:01:02.879
website and maybe skip you want to take

00:01:02.879 --> 00:01:04.720
this one to start but it said we know

00:01:04.720 --> 00:01:07.159
the quantum threat is real we know it's

00:01:07.159 --> 00:01:09.080
preventable so kind of starting the

00:01:09.080 --> 00:01:10.479
conversation there maybe you can kind of

00:01:10.479 --> 00:01:11.960
talk to us a little bit about the

00:01:11.960 --> 00:01:13.600
quantum Computing threat and why it's

00:01:13.600 --> 00:01:15.119
such a big deal in terms of industrial

00:01:15.119 --> 00:01:16.040
cyber

00:01:16.040 --> 00:01:18.240
security absolutely Jeff thanks for

00:01:18.240 --> 00:01:20.799
having us on so uh first we'll start

00:01:20.799 --> 00:01:22.040
with a little bit of background on

00:01:22.040 --> 00:01:24.079
Quantum Computing and uh I'll give

00:01:24.079 --> 00:01:25.880
everybody their theoretical physics

00:01:25.880 --> 00:01:27.799
degrees here so you're all going to get

00:01:27.799 --> 00:01:30.439
uh certificates so quantum Computing is

00:01:30.439 --> 00:01:32.799
a new form of compute um it's different

00:01:32.799 --> 00:01:35.159
than the zeros and ones that we've used

00:01:35.159 --> 00:01:37.240
so if you think about it the the way

00:01:37.240 --> 00:01:39.079
that our computers work today that was a

00:01:39.079 --> 00:01:40.960
human construct so humans came up with

00:01:40.960 --> 00:01:42.680
the idea of hey let's do zeros and ones

00:01:42.680 --> 00:01:44.399
and we have computers that work pretty

00:01:44.399 --> 00:01:47.560
well right got got those um one of the

00:01:47.560 --> 00:01:49.360
problems is that these computers are

00:01:49.360 --> 00:01:51.200
running out of steam they're the

00:01:51.200 --> 00:01:54.360
efficiencies are are sort of diminishing

00:01:54.360 --> 00:01:56.479
and in essence the world needs a new

00:01:56.479 --> 00:01:58.360
form of compute we need to be able to

00:01:58.360 --> 00:02:01.039
launch to the next level because um

00:02:01.039 --> 00:02:02.320
what's happening is they're fitting so

00:02:02.320 --> 00:02:04.439
much on the chip sizes now that that

00:02:04.439 --> 00:02:05.920
their electrons are interfering with

00:02:05.920 --> 00:02:08.399
each other there's heat problems and a

00:02:08.399 --> 00:02:10.720
myriad of issues quantum computers use

00:02:10.720 --> 00:02:13.720
subatomic properties which are things

00:02:13.720 --> 00:02:16.280
like superposition entanglement uh we

00:02:16.280 --> 00:02:18.400
can do more on those later but what

00:02:18.400 --> 00:02:20.440
there are is there ways that things work

00:02:20.440 --> 00:02:22.160
that are that we're not used to

00:02:22.160 --> 00:02:24.720
superposition says that things can be in

00:02:24.720 --> 00:02:27.239
all places at the same time entanglement

00:02:27.239 --> 00:02:29.239
means you can take a couple subatomic

00:02:29.239 --> 00:02:31.440
particles you can separate them by a

00:02:31.440 --> 00:02:34.120
universe and yet they'll still stay

00:02:34.120 --> 00:02:36.239
connected and you can when you reverse

00:02:36.239 --> 00:02:39.080
spinon One Across the Universe at an

00:02:39.080 --> 00:02:41.120
instant not not based on the speed of

00:02:41.120 --> 00:02:43.959
light the other one reverses spin these

00:02:43.959 --> 00:02:46.440
properties are what Drive Quantum

00:02:46.440 --> 00:02:49.599
Computing um Quantum Computing is in its

00:02:49.599 --> 00:02:53.120
early stages however the promise is that

00:02:53.120 --> 00:02:56.360
it will be very very powerful um and it

00:02:56.360 --> 00:02:59.360
will solve key problems and the types of

00:02:59.360 --> 00:03:01.360
problems that solves Jeff are going to

00:03:01.360 --> 00:03:03.959
be multivariate problems so think of

00:03:03.959 --> 00:03:06.440
things where you've got a lot of

00:03:06.440 --> 00:03:09.200
variables to handle um things like

00:03:09.200 --> 00:03:12.280
weather prediction uh genomics uh

00:03:12.280 --> 00:03:15.319
Material Science protein folding uh

00:03:15.319 --> 00:03:17.519
aeronautical design I mean when they

00:03:17.519 --> 00:03:20.200
design an aircraft they have to account

00:03:20.200 --> 00:03:22.720
for every single molecule that hits the

00:03:22.720 --> 00:03:25.159
wings every single one that's a lot of

00:03:25.159 --> 00:03:27.519
variables right so quantum computers are

00:03:27.519 --> 00:03:29.799
great at that now one of the things that

00:03:29.799 --> 00:03:32.319
really good at as well as they're really

00:03:32.319 --> 00:03:34.439
good at breaking the encryption that

00:03:34.439 --> 00:03:37.959
we're all using today so the even this

00:03:37.959 --> 00:03:40.000
session that we're on with you is

00:03:40.000 --> 00:03:42.560
encrypted by standard cryptography that

00:03:42.560 --> 00:03:46.400
by the way was invented in the late 70s

00:03:46.400 --> 00:03:48.400
and quantum computers have the

00:03:48.400 --> 00:03:50.959
capability due to the way they process

00:03:50.959 --> 00:03:53.720
with the subatomic versions they can

00:03:53.720 --> 00:03:56.280
break right through that cryptography at

00:03:56.280 --> 00:03:58.959
when they're powerful enough so our our

00:03:58.959 --> 00:04:01.480
US government has recognized this uh

00:04:01.480 --> 00:04:03.480
Biden signed into law in December an

00:04:03.480 --> 00:04:04.920
initiative that said that all of our

00:04:04.920 --> 00:04:07.000
federal agencies have to upgrade to what

00:04:07.000 --> 00:04:08.760
they're calling post Quantum

00:04:08.760 --> 00:04:10.760
cryptography what that is it's new

00:04:10.760 --> 00:04:13.439
cryptography because they know that when

00:04:13.439 --> 00:04:14.720
quantum computers get here they're going

00:04:14.720 --> 00:04:17.400
to break what we have so this is the

00:04:17.400 --> 00:04:19.840
problem set that exists today basically

00:04:19.840 --> 00:04:21.919
there's a train wreck coming and

00:04:21.919 --> 00:04:24.639
everybody knows it um it may be a few

00:04:24.639 --> 00:04:27.240
years away but a lot of people are

00:04:27.240 --> 00:04:29.120
starting to move now because it's going

00:04:29.120 --> 00:04:32.000
to take a long time to upgrade and by

00:04:32.000 --> 00:04:34.280
the way all of the cryptography in the

00:04:34.280 --> 00:04:36.440
world that's used for public key which

00:04:36.440 --> 00:04:39.039
is the internet all anybody who's on the

00:04:39.039 --> 00:04:42.120
internet in the world has to upgrade the

00:04:42.120 --> 00:04:44.919
cryptography and upgrade the devices 20

00:04:44.919 --> 00:04:46.639
billion devices need to upgrade it's the

00:04:46.639 --> 00:04:48.520
biggest upgrade cycle in computer

00:04:48.520 --> 00:04:50.360
history coming so that's kind of what

00:04:50.360 --> 00:04:52.440
we're up against here well it's

00:04:52.440 --> 00:04:54.600
interesting I mean 20 billion devices

00:04:54.600 --> 00:04:56.440
that's that's obviously kind of

00:04:56.440 --> 00:04:57.800
mind-blowing and that's probably not

00:04:57.800 --> 00:04:59.240
even taking into account really on the

00:04:59.240 --> 00:05:00.639
indust industrial sector all the

00:05:00.639 --> 00:05:02.720
connected Machinery on the plant floor

00:05:02.720 --> 00:05:04.440
and how that's just going to extrapolate

00:05:04.440 --> 00:05:05.800
with the Internet of Things hitting it

00:05:05.800 --> 00:05:08.840
and Industry 4.0 Technologies so when we

00:05:08.840 --> 00:05:11.240
look at the industrial sector what are

00:05:11.240 --> 00:05:12.919
some of the unique challenges maybe

00:05:12.919 --> 00:05:14.360
because I think Quantum Computing might

00:05:14.360 --> 00:05:15.840
be something people are thinking about

00:05:15.840 --> 00:05:18.160
hey I you know I saw the Avengers movies

00:05:18.160 --> 00:05:20.400
um that's not me that doesn't apply but

00:05:20.400 --> 00:05:22.639
obviously it does especially when we've

00:05:22.639 --> 00:05:24.160
got this landscape this threat landscape

00:05:24.160 --> 00:05:26.120
that continues to grow and expand so

00:05:26.120 --> 00:05:27.560
looking specifically at the planed floor

00:05:27.560 --> 00:05:29.720
and the industrial sectors what is a lot

00:05:29.720 --> 00:05:31.680
of this encryption issues what does this

00:05:31.680 --> 00:05:34.280
what does this mean to them I guess sure

00:05:34.280 --> 00:05:36.280
I'll get a start and then Paul jump in

00:05:36.280 --> 00:05:38.280
here as well you know when you think

00:05:38.280 --> 00:05:40.199
about it Jeff all of those Control

00:05:40.199 --> 00:05:42.400
Systems right when you're talking about

00:05:42.400 --> 00:05:44.160
all the control systems that control all

00:05:44.160 --> 00:05:46.880
the machines all of the logistic devices

00:05:46.880 --> 00:05:49.160
um and of course just even standard

00:05:49.160 --> 00:05:53.000
Wi-Fi and iot all of that is vulnerable

00:05:53.000 --> 00:05:54.759
um and by the way manufacturing

00:05:54.759 --> 00:05:56.560
Logistics no different than any other

00:05:56.560 --> 00:05:58.680
industry because we've all standardized

00:05:58.680 --> 00:06:01.000
on this type type of encryption and it's

00:06:01.000 --> 00:06:03.000
been fine for our zero and one computers

00:06:03.000 --> 00:06:05.000
we're using um you know now things get

00:06:05.000 --> 00:06:06.639
hacked once in a while got it and it's

00:06:06.639 --> 00:06:09.560
not good but it it it has generally

00:06:09.560 --> 00:06:12.360
worked so far quantum computers will

00:06:12.360 --> 00:06:14.880
change that Paul you want to add to that

00:06:14.880 --> 00:06:16.599
yeah I thanks skip Jeff one of the

00:06:16.599 --> 00:06:18.400
things I was thinking about when uh you

00:06:18.400 --> 00:06:20.880
were asking that question is you what do

00:06:20.880 --> 00:06:22.840
we do at our core rout here at Q secure

00:06:22.840 --> 00:06:25.440
we're all about Safety and Security and

00:06:25.440 --> 00:06:28.080
when you dial that back to a lot of the

00:06:28.080 --> 00:06:30.080
uh manufacturing Supply chain issues

00:06:30.080 --> 00:06:32.160
that you and your viewers are talking

00:06:32.160 --> 00:06:34.479
about and doing in their daily jobs it

00:06:34.479 --> 00:06:36.039
it boils down to a lot of that same

00:06:36.039 --> 00:06:37.680
thing it's about making sure what you're

00:06:37.680 --> 00:06:40.199
doing is in a secure safe environment

00:06:40.199 --> 00:06:41.880
and very often in manufacturing that's

00:06:41.880 --> 00:06:43.280
that's considered physical you know the

00:06:43.280 --> 00:06:44.680
physical Machinery that you might be

00:06:44.680 --> 00:06:47.000
doing uh and that's clearly very very

00:06:47.000 --> 00:06:48.280
important it has been for you know

00:06:48.280 --> 00:06:50.160
forever but when you look at what we're

00:06:50.160 --> 00:06:52.800
doing uh in more of the digital realm

00:06:52.800 --> 00:06:55.360
that security around data is is equally

00:06:55.360 --> 00:06:57.440
important to the physical safety that

00:06:57.440 --> 00:06:58.919
you and a lot of your viewers are

00:06:58.919 --> 00:07:01.039
dealing with because the the fact that

00:07:01.039 --> 00:07:03.120
we're in a digital Society now and

00:07:03.120 --> 00:07:04.599
everyone that's born today is what they

00:07:04.599 --> 00:07:06.800
call a digital native they're dealing

00:07:06.800 --> 00:07:08.919
with data on such a regular basis and it

00:07:08.919 --> 00:07:11.160
influences our jobs whether they be in

00:07:11.160 --> 00:07:13.240
supply chain manufacturing or technology

00:07:13.240 --> 00:07:16.319
or Finance um data is such a strong

00:07:16.319 --> 00:07:19.479
component on making uh our our society

00:07:19.479 --> 00:07:22.160
work and our businesses including yours

00:07:22.160 --> 00:07:24.400
that what we do and a skip is pointed

00:07:24.400 --> 00:07:25.960
out from the the classical to the

00:07:25.960 --> 00:07:28.280
quantum encryption is is vitally

00:07:28.280 --> 00:07:30.599
important so just a

00:07:30.599 --> 00:07:33.479
a reflection on how our concepts of

00:07:33.479 --> 00:07:35.520
Safety and Security flow over into just

00:07:35.520 --> 00:07:37.240
about an industry including all those

00:07:37.240 --> 00:07:38.479
that you and your viewers are are

00:07:38.479 --> 00:07:40.919
particularly working in interesting you

00:07:40.919 --> 00:07:42.960
know got so many questions flowing

00:07:42.960 --> 00:07:44.400
through my brain here right now but

00:07:44.400 --> 00:07:45.919
trying to keep them in order here a

00:07:45.919 --> 00:07:47.919
little bit so when we look at the

00:07:47.919 --> 00:07:50.120
industrial sector we're still trying to

00:07:50.120 --> 00:07:51.680
catch up with a with a lot of the

00:07:51.680 --> 00:07:53.800
attackers and a lot of how organized and

00:07:53.800 --> 00:07:55.319
specific they can be and how good they

00:07:55.319 --> 00:07:57.960
are getting into these OT networks we

00:07:57.960 --> 00:08:00.080
look at things from the Quantum

00:08:00.080 --> 00:08:01.759
perspective that feels like it's down

00:08:01.759 --> 00:08:04.080
the road a little bit so how should

00:08:04.080 --> 00:08:06.080
industrial cyber security Specialists

00:08:06.080 --> 00:08:07.759
prioritize things in terms of looking at

00:08:07.759 --> 00:08:09.039
where their networks are right now

00:08:09.039 --> 00:08:10.960
keeping them secure but also keeping an

00:08:10.960 --> 00:08:12.720
eye towards the future and how the

00:08:12.720 --> 00:08:15.720
quantum element is going to fit in yeah

00:08:15.720 --> 00:08:18.159
I mean there are a variety of reasons to

00:08:18.159 --> 00:08:20.639
start looking at this now Jeff and and I

00:08:20.639 --> 00:08:22.879
mean this is self-serving so I get it

00:08:22.879 --> 00:08:25.440
but um whether it's you know our company

00:08:25.440 --> 00:08:28.199
or any company um you need to start

00:08:28.199 --> 00:08:30.599
looking at upgrading cryptography so let

00:08:30.599 --> 00:08:32.360
me take a step back so we're talking

00:08:32.360 --> 00:08:34.479
about the quantum threat um and the

00:08:34.479 --> 00:08:36.240
quantum threat as we've discussed does

00:08:36.240 --> 00:08:38.320
have we have some time in that sense and

00:08:38.320 --> 00:08:40.479
I'll tell you two reasons why we need to

00:08:40.479 --> 00:08:44.360
act now one is that um the data as Paul

00:08:44.360 --> 00:08:46.360
was saying is one component of what can

00:08:46.360 --> 00:08:48.640
get stolen now you can also take over

00:08:48.640 --> 00:08:50.760
systems and control systems and that's a

00:08:50.760 --> 00:08:52.399
whole separate issue but let's talk

00:08:52.399 --> 00:08:55.040
about data if data gets stolen today

00:08:55.040 --> 00:08:58.519
it's probably encrypted um but if

00:08:58.519 --> 00:09:00.040
someone has a qu a computer they'll be

00:09:00.040 --> 00:09:02.240
able to decrypt that data in coming

00:09:02.240 --> 00:09:04.480
years and if that data still is valuable

00:09:04.480 --> 00:09:06.920
if it needs 10 15 like if you think of

00:09:06.920 --> 00:09:09.720
banking information 25 years uh military

00:09:09.720 --> 00:09:11.440
nuclear secrets 50 years Healthcare

00:09:11.440 --> 00:09:14.000
information 75 years of protection um

00:09:14.000 --> 00:09:16.000
that's all going to be laid bare and

00:09:16.000 --> 00:09:18.200
that means if you've got five 10 20 or

00:09:18.200 --> 00:09:20.079
30 years of value left on that data and

00:09:20.079 --> 00:09:22.640
it's decrypted well then hackers or or

00:09:22.640 --> 00:09:24.279
nefarious can you know they can do what

00:09:24.279 --> 00:09:26.200
they want with that data so one reason

00:09:26.200 --> 00:09:28.240
to move now is because things that get

00:09:28.240 --> 00:09:30.440
stolen today will be decrypted tomorrow

00:09:30.440 --> 00:09:31.920
that could be valueable information that

00:09:31.920 --> 00:09:34.399
could be a real problem the other issue

00:09:34.399 --> 00:09:36.079
that has come about that all of your

00:09:36.079 --> 00:09:38.480
viewers know about we all know about is

00:09:38.480 --> 00:09:42.880
AI this is a mess I am scared to death

00:09:42.880 --> 00:09:45.320
of AI you saw I don't know if you saw

00:09:45.320 --> 00:09:47.880
just yesterday or day before all the

00:09:47.880 --> 00:09:51.720
articles about worm GPT so now the

00:09:51.720 --> 00:09:54.600
hackers have their own chat GPT that is

00:09:54.600 --> 00:09:57.399
specifically labeled for hacking right

00:09:57.399 --> 00:09:59.600
so they're going to use all of these

00:09:59.600 --> 00:10:01.880
tools just like technology over time it

00:10:01.880 --> 00:10:04.560
always is used for you know harm and

00:10:04.560 --> 00:10:06.760
disruption first before it's even used

00:10:06.760 --> 00:10:08.279
for anything good it's going to happen

00:10:08.279 --> 00:10:11.360
with AI this is coming at us at a speed

00:10:11.360 --> 00:10:14.600
that's amazing and guess what as I said

00:10:14.600 --> 00:10:16.240
earlier we're still working on

00:10:16.240 --> 00:10:19.040
cryptography that was built in the 70s

00:10:19.040 --> 00:10:20.880
you know now we've increased key sizes

00:10:20.880 --> 00:10:24.519
In fairness but that's been from the 70s

00:10:24.519 --> 00:10:26.560
and so you're looking at now vectors

00:10:26.560 --> 00:10:29.640
like AI coming in Plus data being stolen

00:10:29.640 --> 00:10:32.000
and decrypted later against decrypt

00:10:32.000 --> 00:10:34.920
encryption from the 70s so my point is

00:10:34.920 --> 00:10:36.760
companies have to look at upgrading

00:10:36.760 --> 00:10:39.240
cryptography anyway whether for Quantum

00:10:39.240 --> 00:10:41.480
or any other reason let's get out of the

00:10:41.480 --> 00:10:43.480
70s and let's get into the new

00:10:43.480 --> 00:10:45.360
cryptography that nist you know our

00:10:45.360 --> 00:10:46.800
National Institute of Standards

00:10:46.800 --> 00:10:48.839
technology is approving they're saying

00:10:48.839 --> 00:10:51.040
here's a new new cryptography everybody

00:10:51.040 --> 00:10:53.399
you should start using this because we

00:10:53.399 --> 00:10:56.519
know that it can handle uh any of the

00:10:56.519 --> 00:10:58.639
issues that are coming uh instead of the

00:10:58.639 --> 00:11:00.760
old cry cryptography you know a couple

00:11:00.760 --> 00:11:02.240
follow-ups to that I think one of the

00:11:02.240 --> 00:11:04.760
biggest issues with OT cyber security is

00:11:04.760 --> 00:11:06.760
once the attacker gets in it's being

00:11:06.760 --> 00:11:09.079
able to see them and kick them out that

00:11:09.079 --> 00:11:11.480
dwell time is such a big issue because a

00:11:11.480 --> 00:11:12.800
lot of times hackers are sitting in

00:11:12.800 --> 00:11:14.800
there they hit somebody for a ransomware

00:11:14.800 --> 00:11:16.560
attack then they lay low for about eight

00:11:16.560 --> 00:11:18.320
months and then they do it again maybe

00:11:18.320 --> 00:11:19.519
you could talk about how some of these

00:11:19.519 --> 00:11:21.639
Quantum Computing solutions could help

00:11:21.639 --> 00:11:23.519
Rectify that situation and sort of

00:11:23.519 --> 00:11:26.040
improve OT cyber

00:11:26.040 --> 00:11:29.120
visibility yeah absolutely and at the

00:11:29.120 --> 00:11:32.320
moment most of the quantum Computing um

00:11:32.320 --> 00:11:34.600
uh at least in the Cyber sense post

00:11:34.600 --> 00:11:37.480
Quantum cyber is focused on securing

00:11:37.480 --> 00:11:39.560
Communications um and and I'll tell you

00:11:39.560 --> 00:11:42.279
why so Communications really means

00:11:42.279 --> 00:11:45.040
anytime data moves so think of any dated

00:11:45.040 --> 00:11:46.760
movement now that could be over the

00:11:46.760 --> 00:11:49.279
Internet that could be via satellite uh

00:11:49.279 --> 00:11:51.600
that could be other pointto point or um

00:11:51.600 --> 00:11:53.560
it could be even on an internal system

00:11:53.560 --> 00:11:56.880
between servers uh you know on on some

00:11:56.880 --> 00:11:59.200
some infrastructure network but but

00:11:59.200 --> 00:12:00.760
either way it's it's we're focused

00:12:00.760 --> 00:12:03.000
largely on data that's moving um and

00:12:03.000 --> 00:12:05.800
securing the communication channels so

00:12:05.800 --> 00:12:07.320
when those because those are the things

00:12:07.320 --> 00:12:09.160
that are open like this channel we're on

00:12:09.160 --> 00:12:11.279
now is open somebody could grab this

00:12:11.279 --> 00:12:13.199
data now they may not be able to Crypt

00:12:13.199 --> 00:12:14.720
it but they got it same with satellit

00:12:14.720 --> 00:12:16.000
same with everything else satellites

00:12:16.000 --> 00:12:17.560
especially because it's it's it's line

00:12:17.560 --> 00:12:19.480
of sight like you look up at a satellite

00:12:19.480 --> 00:12:21.600
that data is just flowing down right and

00:12:21.600 --> 00:12:23.880
open for anybody to grab but hopefully

00:12:23.880 --> 00:12:26.240
encrypted for you know would safe for a

00:12:26.240 --> 00:12:29.160
while but the the the issue then is we

00:12:29.160 --> 00:12:31.680
move into um as you're talking about

00:12:31.680 --> 00:12:34.760
securing against or detecting so we

00:12:34.760 --> 00:12:37.680
don't detect but there's companies upand

00:12:37.680 --> 00:12:39.480
comers there's a group called Tech

00:12:39.480 --> 00:12:41.279
Slayers who we've partnered with they're

00:12:41.279 --> 00:12:43.480
out of Phoenix that now have really

00:12:43.480 --> 00:12:46.000
Advanced systems that can go in and try

00:12:46.000 --> 00:12:48.199
to find people that are already in your

00:12:48.199 --> 00:12:51.079
network um and so now those folks have

00:12:51.079 --> 00:12:52.880
breached the network they're in they're

00:12:52.880 --> 00:12:54.600
looking around a lot of times they're

00:12:54.600 --> 00:12:56.160
stealing things you don't even know like

00:12:56.160 --> 00:12:57.800
you I mean a couple of the last hacks at

00:12:57.800 --> 00:13:00.399
the federal level uh you know one hack

00:13:00.399 --> 00:13:02.360
they had been in since May the other one

00:13:02.360 --> 00:13:03.600
I don't know if you recall it was about

00:13:03.600 --> 00:13:05.720
a month ago they they they had been in

00:13:05.720 --> 00:13:07.320
uh the Russians had been inside the

00:13:07.320 --> 00:13:10.440
network for 20 years so it's like oh my

00:13:10.440 --> 00:13:13.000
God they have everything so yeah it's

00:13:13.000 --> 00:13:15.360
it's that we would recommend um

00:13:15.360 --> 00:13:17.519
deploying all the latest tools that you

00:13:17.519 --> 00:13:20.160
can to start looking at your network

00:13:20.160 --> 00:13:23.240
making sure that you're um you're always

00:13:23.240 --> 00:13:25.360
probing to see what's what looks like an

00:13:25.360 --> 00:13:28.000
anomaly what's going wrong again on the

00:13:28.000 --> 00:13:29.519
quantum side we haven't looked at

00:13:29.519 --> 00:13:31.959
anybody that's building Quantum systems

00:13:31.959 --> 00:13:34.360
yet to do that but I will tell you Jeff

00:13:34.360 --> 00:13:37.040
your your your your uh uh your your

00:13:37.040 --> 00:13:40.320
question is precient because in my

00:13:40.320 --> 00:13:41.920
belief the only thing that's really ever

00:13:41.920 --> 00:13:43.959
going to stop Quantum and AI is quantum

00:13:43.959 --> 00:13:46.760
and AI So eventually you will have a

00:13:46.760 --> 00:13:49.399
quantum computer on the inside that is

00:13:49.399 --> 00:13:51.480
doing all with AI That's doing all the

00:13:51.480 --> 00:13:53.519
analys to say okay where are we going to

00:13:53.519 --> 00:13:55.240
get attacked who's attacking where think

00:13:55.240 --> 00:13:57.160
of you know it's like zone defense right

00:13:57.160 --> 00:13:58.920
it's always that's the only thing really

00:13:58.920 --> 00:14:00.399
going to stop that that whole initiative

00:14:00.399 --> 00:14:02.759
now that's down the road but I you know

00:14:02.759 --> 00:14:04.600
that I think you're you're a spot

00:14:04.600 --> 00:14:06.639
on well you know we talk about a lot of

00:14:06.639 --> 00:14:07.959
stuff that can definitely keep people up

00:14:07.959 --> 00:14:09.519
at night on this program or in this

00:14:09.519 --> 00:14:12.519
podcast um I think the the potential of

00:14:12.519 --> 00:14:14.519
quantum in terms of identifying a lot of

00:14:14.519 --> 00:14:16.839
those very small data fluctuations that

00:14:16.839 --> 00:14:18.519
we see in the industrial sector

00:14:18.519 --> 00:14:20.079
something going up half a degree doesn't

00:14:20.079 --> 00:14:21.759
sound like a big deal that could be a

00:14:21.759 --> 00:14:23.639
huge deal in a chemical processing plant

00:14:23.639 --> 00:14:24.639
and that could be leading to more

00:14:24.639 --> 00:14:27.440
nefarious um hacking motives down the

00:14:27.440 --> 00:14:29.519
line so the greater sensitivity will be

00:14:29.519 --> 00:14:31.480
a big deal there also you know you

00:14:31.480 --> 00:14:33.720
talked about Ai and how AI is what can

00:14:33.720 --> 00:14:36.279
stop AI I know it's it is nerve-wracking

00:14:36.279 --> 00:14:37.639
when you think about all the things that

00:14:37.639 --> 00:14:39.320
these tools can do in the hands of the

00:14:39.320 --> 00:14:41.560
bad guys but there's a lot of things the

00:14:41.560 --> 00:14:44.000
good guys can do with AI as well from a

00:14:44.000 --> 00:14:45.959
cyber security perspective I was hoping

00:14:45.959 --> 00:14:47.240
maybe you could talk about some of the

00:14:47.240 --> 00:14:48.600
things either you're working on you've

00:14:48.600 --> 00:14:50.920
seen or you think could develop for the

00:14:50.920 --> 00:14:53.240
white hats when it comes to using AI

00:14:53.240 --> 00:14:56.320
tools I think when you look at uh What

00:14:56.320 --> 00:14:59.279
uh Q secure can offer and and and the

00:14:59.279 --> 00:15:01.920
security components of AI that are built

00:15:01.920 --> 00:15:05.720
into uh our Quantum Quantum resilience

00:15:05.720 --> 00:15:08.480
it's a continually learning process and

00:15:08.480 --> 00:15:11.959
what we've done is uh developed a system

00:15:11.959 --> 00:15:13.839
that is what we like to call crypto

00:15:13.839 --> 00:15:15.600
agile and that means when you're looking

00:15:15.600 --> 00:15:17.279
at all of the the variances that you

00:15:17.279 --> 00:15:19.440
have in your security measures or even

00:15:19.440 --> 00:15:20.920
those measures that are measuring for

00:15:20.920 --> 00:15:24.399
you um you're looking an ability of AI

00:15:24.399 --> 00:15:27.839
to help drastically increase the amount

00:15:27.839 --> 00:15:30.279
of active defense we have and the amount

00:15:30.279 --> 00:15:32.680
of keys that we have to be able to

00:15:32.680 --> 00:15:35.440
continually have fallback redundancy so

00:15:35.440 --> 00:15:37.000
that when there is an attack happening

00:15:37.000 --> 00:15:38.880
or when there is something happening we

00:15:38.880 --> 00:15:42.440
are always able to recognize uh a new

00:15:42.440 --> 00:15:43.360
set

00:15:43.360 --> 00:15:46.440
of evaluated or encrypted keys that we

00:15:46.440 --> 00:15:49.319
can use to to do that so I think it's a

00:15:49.319 --> 00:15:51.399
um It's A Brave New World for what AI is

00:15:51.399 --> 00:15:52.920
bringing but when you develop it with

00:15:52.920 --> 00:15:54.920
Quantum it's uh there's there's a lot of

00:15:54.920 --> 00:15:56.880
potential for for good as well as bad

00:15:56.880 --> 00:15:58.600
there skip did you want to jump in that

00:15:58.600 --> 00:16:01.360
anymore yeah I can jump on that too so

00:16:01.360 --> 00:16:04.399
Jee essentially as Paul was describing

00:16:04.399 --> 00:16:07.720
um idea being that you need AI to

00:16:07.720 --> 00:16:10.720
predict and change things because humans

00:16:10.720 --> 00:16:13.920
aren't fast enough so an example in our

00:16:13.920 --> 00:16:17.000
product we've built AI in so you

00:16:17.000 --> 00:16:20.040
actually can change cryptography now and

00:16:20.040 --> 00:16:22.959
uh you can move it so that if let's say

00:16:22.959 --> 00:16:25.160
um on the nist algorithms these are new

00:16:25.160 --> 00:16:26.440
the new crypto nist is doing for

00:16:26.440 --> 00:16:27.839
instance they have four new algorithms

00:16:27.839 --> 00:16:29.759
that looks like they're going to approve

00:16:29.759 --> 00:16:31.759
um you know you need to be able to use

00:16:31.759 --> 00:16:33.199
all four and you need to be able to use

00:16:33.199 --> 00:16:34.800
different key sizes you need to be able

00:16:34.800 --> 00:16:37.560
to switch those and AI can do that as it

00:16:37.560 --> 00:16:39.279
looks and says okay wait I see a vector

00:16:39.279 --> 00:16:40.800
open out here let me upgrade that

00:16:40.800 --> 00:16:42.759
cryptography let me switch this over

00:16:42.759 --> 00:16:44.519
here because I think there's a a you

00:16:44.519 --> 00:16:47.480
know a DDOS attack over there and that's

00:16:47.480 --> 00:16:48.680
how you're going to use it you're going

00:16:48.680 --> 00:16:51.480
to use it and again I go back to and you

00:16:51.480 --> 00:16:53.319
you asked earlier Jeff why do people

00:16:53.319 --> 00:16:56.279
need to do this now because the you

00:16:56.279 --> 00:16:58.959
think about it the the existing encryp

00:16:58.959 --> 00:17:01.000
is like a flat file it's like an Excel

00:17:01.000 --> 00:17:03.480
file versus an Oracle database two

00:17:03.480 --> 00:17:05.400
different worlds Excel file is flat

00:17:05.400 --> 00:17:07.520
Oracle database is relational right you

00:17:07.520 --> 00:17:09.799
do tons of stuff our existing encryption

00:17:09.799 --> 00:17:11.919
is flat it's a single mathematical

00:17:11.919 --> 00:17:14.160
transaction it's not changeable you're

00:17:14.160 --> 00:17:16.160
not changing crypto at all now all

00:17:16.160 --> 00:17:17.720
you're doing is leaving your own stuff

00:17:17.720 --> 00:17:19.679
there and hoping it works you've got to

00:17:19.679 --> 00:17:21.919
get into new cryptography and be able to

00:17:21.919 --> 00:17:23.439
change it and have it automatically

00:17:23.439 --> 00:17:26.079
change the AI or machine learning on the

00:17:26.079 --> 00:17:28.079
Fly that's how you're going to build

00:17:28.079 --> 00:17:31.000
defense is against against AI because

00:17:31.000 --> 00:17:32.919
those vectors that the bad guys are

00:17:32.919 --> 00:17:34.720
using with AI they're going to get

00:17:34.720 --> 00:17:37.160
stronger and faster and better and

00:17:37.160 --> 00:17:40.080
smarter and and this is why again we

00:17:40.080 --> 00:17:42.280
can't wait around any any of your

00:17:42.280 --> 00:17:44.440
companies listening to this podcast

00:17:44.440 --> 00:17:46.360
start looking at new cryptography today

00:17:46.360 --> 00:17:48.799
you've got to start embracing it because

00:17:48.799 --> 00:17:50.720
you don't want to get caught behind that

00:17:50.720 --> 00:17:53.360
tsunami like Paul's talking about um we

00:17:53.360 --> 00:17:55.440
can't emphasize enough that you know

00:17:55.440 --> 00:17:57.280
it's it's kind of like I remember seeing

00:17:57.280 --> 00:17:59.840
a meme Jeff you to laugh at this where

00:17:59.840 --> 00:18:03.120
it showed uh budget budget before uh

00:18:03.120 --> 00:18:05.120
Cyber attack and it had like it showed a

00:18:05.120 --> 00:18:07.440
picture of like three pennies budget

00:18:07.440 --> 00:18:09.799
after Cyber attack like a million

00:18:09.799 --> 00:18:11.799
dollars right in other words you don't

00:18:11.799 --> 00:18:14.480
want to budget and go oh well we just

00:18:14.480 --> 00:18:16.039
got breached and lost everything but

00:18:16.039 --> 00:18:18.320
let's put some good cryptography in now

00:18:18.320 --> 00:18:19.919
you know again it's it's it's a new

00:18:19.919 --> 00:18:21.799
world and it's got to be

00:18:21.799 --> 00:18:24.320
messy yeah just just to add to that Skip

00:18:24.320 --> 00:18:27.799
it's uh we talk about security and and

00:18:27.799 --> 00:18:30.080
playing defense well you have to be on

00:18:30.080 --> 00:18:32.000
offense to be able to have a good

00:18:32.000 --> 00:18:33.679
defense in this particular case meaning

00:18:33.679 --> 00:18:36.480
you need to start now and be proactive

00:18:36.480 --> 00:18:38.080
uh it's just it'll be too late if you

00:18:38.080 --> 00:18:40.919
wait way too much longer no great great

00:18:40.919 --> 00:18:42.720
points and you know to kind of echo the

00:18:42.720 --> 00:18:45.240
sentiment of that you know that comic or

00:18:45.240 --> 00:18:47.240
that's the the gift that you saw I mean

00:18:47.240 --> 00:18:48.679
we've had people come on the program and

00:18:48.679 --> 00:18:51.159
talk about investment in cyber security

00:18:51.159 --> 00:18:53.000
within an Enterprise didn't increase

00:18:53.000 --> 00:18:55.039
until after a ransomware attack because

00:18:55.039 --> 00:18:56.480
they have to report that stuff in a

00:18:56.480 --> 00:18:59.080
quarterly meeting in uh reports annual

00:18:59.080 --> 00:19:00.480
reports things like that they don't want

00:19:00.480 --> 00:19:01.720
to deal with it so they make the

00:19:01.720 --> 00:19:03.159
investment it's too bad it happened

00:19:03.159 --> 00:19:04.760
after the fact but it's at least

00:19:04.760 --> 00:19:06.280
encouraging to see that more of that is

00:19:06.280 --> 00:19:08.679
taking place at this point um you know

00:19:08.679 --> 00:19:09.840
one of the things I wanted to run past

00:19:09.840 --> 00:19:11.240
you guys too and all of the stuff that

00:19:11.240 --> 00:19:12.120
you're talking about I just want to

00:19:12.120 --> 00:19:13.880
reiterate what you said there this is an

00:19:13.880 --> 00:19:16.440
issue now this isn't tomorrow's problem

00:19:16.440 --> 00:19:18.840
this is going on right now a lot of

00:19:18.840 --> 00:19:20.400
manufacturing consider themselves

00:19:20.400 --> 00:19:22.360
smaller companies they consider their

00:19:22.360 --> 00:19:23.960
their what they're doing their process

00:19:23.960 --> 00:19:26.000
their products not important enough to

00:19:26.000 --> 00:19:27.760
get the attention of hackers we know

00:19:27.760 --> 00:19:29.520
that's not the case we know the way

00:19:29.520 --> 00:19:31.320
Supply chains are integrated everyone's

00:19:31.320 --> 00:19:33.760
a Target where what advice would you

00:19:33.760 --> 00:19:35.400
offer to some of these smaller firms

00:19:35.400 --> 00:19:37.280
these smaller Enterprises in terms of

00:19:37.280 --> 00:19:39.320
where do I start because when you start

00:19:39.320 --> 00:19:41.360
digging into cyber security it can be

00:19:41.360 --> 00:19:43.240
really daunting especially when you get

00:19:43.240 --> 00:19:45.559
into terms like Quantum Computing and in

00:19:45.559 --> 00:19:47.720
Quantum encryption where should people

00:19:47.720 --> 00:19:48.760
where should they start what's the low

00:19:48.760 --> 00:19:49.679
hanging

00:19:49.679 --> 00:19:52.520
fruit yeah I'll start Paul you jump in

00:19:52.520 --> 00:19:54.840
on this as well so the first thing to do

00:19:54.840 --> 00:19:56.480
is understand the cryptography you have

00:19:56.480 --> 00:19:58.799
in your network okay um and where it

00:19:58.799 --> 00:20:00.400
lives because cryptography lives in a

00:20:00.400 --> 00:20:02.360
lot of places it can live on servers it

00:20:02.360 --> 00:20:04.480
can live on applications it can live on

00:20:04.480 --> 00:20:06.720
Communications um and and actually I

00:20:06.720 --> 00:20:08.520
said I shouldn't say can it lives on all

00:20:08.520 --> 00:20:10.840
those things um so every application

00:20:10.840 --> 00:20:13.480
every um device um every Communications

00:20:13.480 --> 00:20:16.960
Channel um every server has cryptography

00:20:16.960 --> 00:20:18.640
somewhere in it you know Cisco will have

00:20:18.640 --> 00:20:20.760
cryptography uh you'll use TLS for

00:20:20.760 --> 00:20:23.280
communications between devices iot may

00:20:23.280 --> 00:20:26.400
have cryptography now um and by the way

00:20:26.400 --> 00:20:27.720
uh there's the new initiative just came

00:20:27.720 --> 00:20:29.679
out yesterday that now there's going to

00:20:29.679 --> 00:20:33.320
be a consumer label on iot uh that will

00:20:33.320 --> 00:20:34.559
give it a cryptograph not a

00:20:34.559 --> 00:20:36.600
cryptographic give it a kind of a

00:20:36.600 --> 00:20:39.240
standard rating of is it how secure it

00:20:39.240 --> 00:20:42.080
is just came out yesterday um so you

00:20:42.080 --> 00:20:44.280
could see the movement the point is is

00:20:44.280 --> 00:20:45.760
that you've got all of these different

00:20:45.760 --> 00:20:48.679
forms and places first thing to do is

00:20:48.679 --> 00:20:50.520
begin to understand what you have and

00:20:50.520 --> 00:20:52.880
where it is now you you talk Jeff about

00:20:52.880 --> 00:20:55.159
the integration of the supply chain

00:20:55.159 --> 00:20:58.080
absolutely and if if your supplier to to

00:20:58.080 --> 00:20:59.559
to a larger company whether it's

00:20:59.559 --> 00:21:01.679
Automotive or it's retail or you're in

00:21:01.679 --> 00:21:03.480
one of those uh whatever you're

00:21:03.480 --> 00:21:05.600
supplying you can bet the biggest

00:21:05.600 --> 00:21:07.280
companies in your industry are going to

00:21:07.280 --> 00:21:08.679
start changing things and they're going

00:21:08.679 --> 00:21:10.039
to come down and they're going to make

00:21:10.039 --> 00:21:12.120
their all of their vendors and all of

00:21:12.120 --> 00:21:14.480
their Partners change as well and this

00:21:14.480 --> 00:21:16.240
is you know like if you're in Walmart's

00:21:16.240 --> 00:21:19.600
chain as everybody knows you you do what

00:21:19.600 --> 00:21:21.400
they say when they say hey we need this

00:21:21.400 --> 00:21:23.120
everybody go to this you go to that

00:21:23.120 --> 00:21:25.080
otherwise you're out of the chain but

00:21:25.080 --> 00:21:27.480
the idea being is you need to look at

00:21:27.480 --> 00:21:30.480
your own phography and and I will tell

00:21:30.480 --> 00:21:32.120
you guess what it's all Quantum

00:21:32.120 --> 00:21:33.840
vulnerable because none of it was built

00:21:33.840 --> 00:21:36.360
to to to defend against Quantum so it's

00:21:36.360 --> 00:21:37.760
all going to be vulnerable but first

00:21:37.760 --> 00:21:39.760
step is to start studying what you have

00:21:39.760 --> 00:21:41.760
second step is to look at remediation

00:21:41.760 --> 00:21:43.039
where am I going to start plugging the

00:21:43.039 --> 00:21:45.480
holes third step is to put in new crypto

00:21:45.480 --> 00:21:47.279
and you could do all of those things we

00:21:47.279 --> 00:21:49.320
would suggest testing new crypto right

00:21:49.320 --> 00:21:51.840
away uh it's easy to test and with

00:21:51.840 --> 00:21:53.520
groups like ours we can do tests in a

00:21:53.520 --> 00:21:55.840
few days for you right to start that in

00:21:55.840 --> 00:21:58.080
the meantime you can deploy some of your

00:21:58.080 --> 00:22:01.200
your um your analysis tools to like like

00:22:01.200 --> 00:22:03.320
I mentioned text layers earlier that's a

00:22:03.320 --> 00:22:05.159
group those guys will go in and they'll

00:22:05.159 --> 00:22:06.720
do a red team they'll look at your

00:22:06.720 --> 00:22:08.120
cryptography they'll give you a report

00:22:08.120 --> 00:22:09.400
on what it is they'll give you a report

00:22:09.400 --> 00:22:11.720
on vulnerabilities that's how I'd say

00:22:11.720 --> 00:22:15.360
you get started Paul yeah I just echoing

00:22:15.360 --> 00:22:17.400
what skip was saying that uh you can

00:22:17.400 --> 00:22:18.919
start small you don't have to eat the

00:22:18.919 --> 00:22:20.679
whale in one bite you just take a bite

00:22:20.679 --> 00:22:23.279
at a time and some of that means you

00:22:23.279 --> 00:22:25.200
know as as skip pointed out doing a

00:22:25.200 --> 00:22:26.480
little bit of understanding of of what

00:22:26.480 --> 00:22:28.200
your needs are and if you take a

00:22:28.200 --> 00:22:30.159
particularly small piece that might be

00:22:30.159 --> 00:22:32.320
very critical information and you just

00:22:32.320 --> 00:22:34.520
do a proof of concept concept maybe with

00:22:34.520 --> 00:22:36.960
it uh to get an understanding of of how

00:22:36.960 --> 00:22:38.799
that might work in your larger system

00:22:38.799 --> 00:22:40.400
you don't have to do a rip and replace

00:22:40.400 --> 00:22:41.679
you don't have to pull out all of your

00:22:41.679 --> 00:22:44.320
Hardware you can use a software solution

00:22:44.320 --> 00:22:46.880
that is able to drop in and be

00:22:46.880 --> 00:22:48.240
compatible with a lot of Legacy

00:22:48.240 --> 00:22:50.520
environments to be able to really see I

00:22:50.520 --> 00:22:52.679
don't have to as I said eat the whale in

00:22:52.679 --> 00:22:54.799
one bite uh you there there are

00:22:54.799 --> 00:22:56.880
solutions out there including ours that

00:22:56.880 --> 00:22:59.039
that give you an ability to to do this

00:22:59.039 --> 00:23:02.919
in a very uh uh thorough but piece by

00:23:02.919 --> 00:23:04.600
piece manner so you're taking off small

00:23:04.600 --> 00:23:07.120
bites to recognize uh what the the

00:23:07.120 --> 00:23:08.400
bigger picture would be but you have to

00:23:08.400 --> 00:23:10.000
start somewhere and starting with

00:23:10.000 --> 00:23:11.440
looking at what your architecture is

00:23:11.440 --> 00:23:13.600
what the existing encryption systems are

00:23:13.600 --> 00:23:15.440
and how you can build a plan and a road

00:23:15.440 --> 00:23:17.440
map to get there over time it doesn't

00:23:17.440 --> 00:23:18.760
have to be a One-Stop shop and you're

00:23:18.760 --> 00:23:20.720
and you're done it's it can be a journey

00:23:20.720 --> 00:23:22.440
that we we could help you with

00:23:22.440 --> 00:23:23.679
absolutely you know I think that's a

00:23:23.679 --> 00:23:25.880
great point in terms of it anything

00:23:25.880 --> 00:23:27.240
essentially anything we're doing right

00:23:27.240 --> 00:23:29.080
now is positive anything we can do to

00:23:29.080 --> 00:23:31.039
make the Hacker's job a little bit more

00:23:31.039 --> 00:23:34.000
difficult in protecting your system your

00:23:34.000 --> 00:23:35.960
data your Enterprise it's all going to

00:23:35.960 --> 00:23:37.960
play a role even if it's not as much as

00:23:37.960 --> 00:23:39.840
you may think it should be to start with

00:23:39.840 --> 00:23:41.840
just get the ball rolling and we can go

00:23:41.840 --> 00:23:44.159
from there I think it's a great Point um

00:23:44.159 --> 00:23:45.559
want to kind of gauge you guys' thoughts

00:23:45.559 --> 00:23:48.039
on another um topic that comes up a lot

00:23:48.039 --> 00:23:49.400
in terms of cyber security in the

00:23:49.400 --> 00:23:51.080
industrial sector and that's really

00:23:51.080 --> 00:23:53.640
protecting the cloud um a lot of

00:23:53.640 --> 00:23:55.279
Industrial Enterprises have navigated

00:23:55.279 --> 00:23:56.919
towards the cloud they rely on it very

00:23:56.919 --> 00:23:58.240
heavily in terms of storm storing and

00:23:58.240 --> 00:24:00.840
sharing data but security sometimes

00:24:00.840 --> 00:24:02.880
becomes as surprising as it may sound a

00:24:02.880 --> 00:24:05.000
forgotten Factor I'd love to get your

00:24:05.000 --> 00:24:06.840
thoughts in terms of what manufacturers

00:24:06.840 --> 00:24:08.360
can do to make sure their cloud is

00:24:08.360 --> 00:24:10.320
secure or maybe just some best practices

00:24:10.320 --> 00:24:13.840
that you could uh pass along so CL cloud

00:24:13.840 --> 00:24:16.559
is is all the rage right and uh although

00:24:16.559 --> 00:24:18.120
there is some movement to to move back

00:24:18.120 --> 00:24:20.440
into to say private cloud or or back on

00:24:20.440 --> 00:24:23.360
the servers but nonetheless you know AWS

00:24:23.360 --> 00:24:25.679
Microsoft Google IBM you know they all

00:24:25.679 --> 00:24:27.200
have giant clouds of course and there's

00:24:27.200 --> 00:24:29.200
International on as well you know

00:24:29.200 --> 00:24:32.320
Alibaba B and these guys um but but

00:24:32.320 --> 00:24:35.559
Cloud essentially is a absolute you know

00:24:35.559 --> 00:24:38.240
weak point for security because you're

00:24:38.240 --> 00:24:40.520
doing everything over outside

00:24:40.520 --> 00:24:42.720
Communications channels right so you're

00:24:42.720 --> 00:24:44.440
thinking about if you know if you're if

00:24:44.440 --> 00:24:45.960
you're pulling things and putting things

00:24:45.960 --> 00:24:48.600
on servers elsewhere um those are all

00:24:48.600 --> 00:24:50.360
going over standard Communications with

00:24:50.360 --> 00:24:52.640
standard encryption and Ven and when

00:24:52.640 --> 00:24:56.120
audience yes in the 70s um and so it

00:24:56.120 --> 00:24:58.080
there are some severe issues we're

00:24:58.080 --> 00:25:00.240
working very closely with AWS we've been

00:25:00.240 --> 00:25:02.880
approved by AWS on a variety of fronts

00:25:02.880 --> 00:25:05.000
and we're working closely with them uh

00:25:05.000 --> 00:25:06.520
so that they can you know look at

00:25:06.520 --> 00:25:08.480
securing the cloud and putting in this

00:25:08.480 --> 00:25:11.279
sort of cryptography um and and you know

00:25:11.279 --> 00:25:14.880
moving to the advanced stuff um for your

00:25:14.880 --> 00:25:17.679
companies for you the partners you have

00:25:17.679 --> 00:25:19.720
here best thing to do is start looking

00:25:19.720 --> 00:25:22.240
at at their their Cloud posture uh look

00:25:22.240 --> 00:25:24.679
at the cryptography that's being used uh

00:25:24.679 --> 00:25:26.799
over you know to to access that cloud

00:25:26.799 --> 00:25:28.760
where it might be a v type thing which

00:25:28.760 --> 00:25:31.120
is by the way a little better but still

00:25:31.120 --> 00:25:33.880
very hackable uh and then look at things

00:25:33.880 --> 00:25:35.840
like applying postquantum or Quantum

00:25:35.840 --> 00:25:37.960
resilient cryptography to that for

00:25:37.960 --> 00:25:39.919
instance if it's a web-based cloud you

00:25:39.919 --> 00:25:42.120
could actually create a quantum Channel

00:25:42.120 --> 00:25:44.000
very very easily there it's not a

00:25:44.000 --> 00:25:46.640
problem and as Paul was saying with our

00:25:46.640 --> 00:25:48.559
product specifically you don't change

00:25:48.559 --> 00:25:50.640
anything you actually just overlay this

00:25:50.640 --> 00:25:52.240
or you tunnel in the existing encryption

00:25:52.240 --> 00:25:53.760
so you keep the encryption you have

00:25:53.760 --> 00:25:55.640
don't even change it but in the same

00:25:55.640 --> 00:25:57.279
assessment like we talked about just in

00:25:57.279 --> 00:26:00.039
that early question Jeff you know you

00:26:00.039 --> 00:26:02.320
want to assess your Cloud posture and

00:26:02.320 --> 00:26:04.200
your vulnerabilities the cryptography

00:26:04.200 --> 00:26:06.640
you're using and talk with your Cloud

00:26:06.640 --> 00:26:08.840
partner um you know your cloud provider

00:26:08.840 --> 00:26:10.720
and say look what are you guys doing in

00:26:10.720 --> 00:26:13.120
postquantum how are you guys deploying

00:26:13.120 --> 00:26:15.520
new algorithms to make sure that my data

00:26:15.520 --> 00:26:17.440
is going to be safe um and the

00:26:17.440 --> 00:26:20.720
communications between uh your your you

00:26:20.720 --> 00:26:22.240
know your sites you know your data

00:26:22.240 --> 00:26:24.840
centers and my servers how are we going

00:26:24.840 --> 00:26:26.440
to make sure those Communications are

00:26:26.440 --> 00:26:29.919
secure we say take some responsibility

00:26:29.919 --> 00:26:31.760
smaller companies or companies that use

00:26:31.760 --> 00:26:34.159
the cloud because it's going to be on

00:26:34.159 --> 00:26:37.240
you if there's a hack anyway but um the

00:26:37.240 --> 00:26:39.279
cloud providers are looking at it I mean

00:26:39.279 --> 00:26:41.000
they're they're trying to to move as

00:26:41.000 --> 00:26:43.039
well I think we need everybody on the

00:26:43.039 --> 00:26:45.080
same page to start pushing the

00:26:45.080 --> 00:26:47.360
agenda makes

00:26:47.360 --> 00:26:50.320
sense I just add in there real quickly

00:26:50.320 --> 00:26:52.120
that you know the cloud by its nature

00:26:52.120 --> 00:26:53.799
sounds poorest because it's going up

00:26:53.799 --> 00:26:55.320
into the cloud but it's essentially just

00:26:55.320 --> 00:26:56.799
a channel and a pipe that works up

00:26:56.799 --> 00:26:58.880
through there uh these days in wrapped

00:26:58.880 --> 00:27:01.520
in TSL to be able to provide it and if

00:27:01.520 --> 00:27:03.480
you look for solutions that aren't just

00:27:03.480 --> 00:27:05.279
Patchwork but ones that actually do is

00:27:05.279 --> 00:27:07.480
is Skip pointed out have a wraparound

00:27:07.480 --> 00:27:09.760
effect and can layer over that TSL with

00:27:09.760 --> 00:27:12.360
something like a qsl environment uh that

00:27:12.360 --> 00:27:15.679
can very easily uh and simply uh protect

00:27:15.679 --> 00:27:17.399
it uh we we've done some work in that

00:27:17.399 --> 00:27:18.559
regard with satellites where we've

00:27:18.559 --> 00:27:20.360
proven that we can have secure channels

00:27:20.360 --> 00:27:23.279
going up through the cloud uh to uh to

00:27:23.279 --> 00:27:25.600
Leo and Geo orbits to to protect that

00:27:25.600 --> 00:27:27.799
data in a cloud environment so it's it

00:27:27.799 --> 00:27:30.520
possible and it's being done right now

00:27:30.520 --> 00:27:32.159
yeah it's possible we just need to pay

00:27:32.159 --> 00:27:33.919
attention to it make sure we're not just

00:27:33.919 --> 00:27:37.120
relying on Amazon or Microsoft or Google

00:27:37.120 --> 00:27:38.720
or whomever you're using to take care of

00:27:38.720 --> 00:27:40.880
it it's it's a shared responsibility

00:27:40.880 --> 00:27:43.559
without a doubt so guys this has been

00:27:43.559 --> 00:27:45.200
great we've talked a lot about Q secure

00:27:45.200 --> 00:27:46.559
and the things you guys do we've talked

00:27:46.559 --> 00:27:47.919
about different trends that are taking

00:27:47.919 --> 00:27:49.960
place throughout cyber security anything

00:27:49.960 --> 00:27:51.200
else you'd like to add on either one of

00:27:51.200 --> 00:27:53.880
those fronts as we kind of wrap stuff up

00:27:53.880 --> 00:27:55.960
here you know I would say just what

00:27:55.960 --> 00:27:58.120
we've emphasized through the whole call

00:27:58.120 --> 00:28:00.799
um it's time now for the cryptographic

00:28:00.799 --> 00:28:03.080
upgrade it's time to start looking at at

00:28:03.080 --> 00:28:05.600
your cryptography it's time to start

00:28:05.600 --> 00:28:08.799
thinking of change putting in budgets um

00:28:08.799 --> 00:28:10.279
we're not saying that you need to do

00:28:10.279 --> 00:28:13.320
everything at once but at least you know

00:28:13.320 --> 00:28:14.960
that if you start down that road you're

00:28:14.960 --> 00:28:16.399
going to give yourself the best chance

00:28:16.399 --> 00:28:18.480
of protection the other thing it does

00:28:18.480 --> 00:28:20.000
become of a bit of a nice branding

00:28:20.000 --> 00:28:21.519
element for instance if you're working

00:28:21.519 --> 00:28:24.000
with Quantum safe cryptography you could

00:28:24.000 --> 00:28:25.960
you know that's not a bad press release

00:28:25.960 --> 00:28:28.120
to put out to your stake holders or your

00:28:28.120 --> 00:28:30.440
investors if you're public or private um

00:28:30.440 --> 00:28:32.200
and let them know guys we take this

00:28:32.200 --> 00:28:34.640
seriously um you know we're also seeing

00:28:34.640 --> 00:28:36.440
that there are um companies are being

00:28:36.440 --> 00:28:38.120
held more responsible boards are being

00:28:38.120 --> 00:28:40.760
held more responsible for cyber breaches

00:28:40.760 --> 00:28:42.320
um now there's more reporting at the

00:28:42.320 --> 00:28:43.799
federal level if you've been breached

00:28:43.799 --> 00:28:45.720
it's mandatory now it's no longer an

00:28:45.720 --> 00:28:48.240
option these are all things that we're

00:28:48.240 --> 00:28:50.279
all saying look you know companies have

00:28:50.279 --> 00:28:51.880
got to take responsibility for this

00:28:51.880 --> 00:28:53.120
because in the past it was kind of like

00:28:53.120 --> 00:28:55.279
oh we got hacked it's bad cost money but

00:28:55.279 --> 00:28:57.720
you know nobody really gets blamed right

00:28:57.720 --> 00:29:00.000
it's pretty serious now so you want to

00:29:00.000 --> 00:29:01.880
get on the front side of it and it's

00:29:01.880 --> 00:29:03.519
like anything else you want to show that

00:29:03.519 --> 00:29:04.960
you're diligent you want to show that

00:29:04.960 --> 00:29:06.880
you're ahead of the curb think of it as

00:29:06.880 --> 00:29:08.679
R&D and Innovation just like you're

00:29:08.679 --> 00:29:09.960
innovating with your products and

00:29:09.960 --> 00:29:12.159
services innovate with your security

00:29:12.159 --> 00:29:13.720
because if you don't innovate then

00:29:13.720 --> 00:29:15.519
you're going to be using the old stuff

00:29:15.519 --> 00:29:16.720
and if you use the old stuff and

00:29:16.720 --> 00:29:18.720
something happens believe me you're

00:29:18.720 --> 00:29:21.360
going to have people all over you saying

00:29:21.360 --> 00:29:23.840
why didn't you do any of these things

00:29:23.840 --> 00:29:25.440
you know it can't be because we were too

00:29:25.440 --> 00:29:27.840
busy or I don't know

00:29:27.840 --> 00:29:30.320
it's it's time now so yeah we would just

00:29:30.320 --> 00:29:32.799
recommend everybody start moving on

00:29:32.799 --> 00:29:35.240
that I think Skip stole my playbook for

00:29:35.240 --> 00:29:36.880
that

00:29:36.880 --> 00:29:39.240
answer I was G the one word that came to

00:29:39.240 --> 00:29:41.000
mind Jeff when you asked about you know

00:29:41.000 --> 00:29:43.240
what what can we you know do now there's

00:29:43.240 --> 00:29:45.480
opportunity we often look at the threats

00:29:45.480 --> 00:29:47.519
and we look at the negatives and you the

00:29:47.519 --> 00:29:50.240
you have to with compliance but Skip's

00:29:50.240 --> 00:29:51.960
right there's a fiduciary opportunity

00:29:51.960 --> 00:29:53.279
there where there is a responsibility

00:29:53.279 --> 00:29:55.159
for people to do it but there's also a

00:29:55.159 --> 00:29:57.440
commercial opportunity to get their

00:29:57.440 --> 00:29:58.720
first and to be able to show your

00:29:58.720 --> 00:30:00.480
customers and your shareholders and your

00:30:00.480 --> 00:30:02.640
employees that security and safety

00:30:02.640 --> 00:30:04.679
matters not just the physical security

00:30:04.679 --> 00:30:06.080
like we talked about early from the

00:30:06.080 --> 00:30:08.799
manufacturing and Industrial sense but

00:30:08.799 --> 00:30:10.919
the security that you can provide from a

00:30:10.919 --> 00:30:13.480
data perspective and the importance of

00:30:13.480 --> 00:30:15.320
of uh anything that you have that's

00:30:15.320 --> 00:30:17.480
going to be be data related as well and

00:30:17.480 --> 00:30:19.360
then the last point I would make is

00:30:19.360 --> 00:30:21.000
we're all doing something that works

00:30:21.000 --> 00:30:22.559
across a shared vision and a shared

00:30:22.559 --> 00:30:24.760
Mission and that is at the core of what

00:30:24.760 --> 00:30:27.919
we do around security and safety uh it

00:30:27.919 --> 00:30:30.600
delves into privacy as well too uh but

00:30:30.600 --> 00:30:32.279
we're doing this if it's either at a

00:30:32.279 --> 00:30:33.720
very very high level I'm making sure

00:30:33.720 --> 00:30:35.600
that the government and we're we're all

00:30:35.600 --> 00:30:36.799
trying to help the government be

00:30:36.799 --> 00:30:38.679
protected from foreign nation states or

00:30:38.679 --> 00:30:41.159
Bad actors down to our individual uh

00:30:41.159 --> 00:30:43.840
concerns and and and protecting our our

00:30:43.840 --> 00:30:45.559
schools our environments our communities

00:30:45.559 --> 00:30:48.640
our our families uh it spans the gamut

00:30:48.640 --> 00:30:51.279
so it's it's a Shear desire to um to

00:30:51.279 --> 00:30:53.120
make sure our society and way of life

00:30:53.120 --> 00:30:55.559
can be protected with these new threats

00:30:55.559 --> 00:30:57.399
and opportunities that AI Mach machine

00:30:57.399 --> 00:31:00.320
learning Quantum Computing all provide

00:31:00.320 --> 00:31:03.120
so last question guys got to ask this

00:31:03.120 --> 00:31:04.519
we've talked about some kind of scary

00:31:04.519 --> 00:31:06.200
stuff and you guys work on a little bit

00:31:06.200 --> 00:31:07.919
different plane I think than a lot of

00:31:07.919 --> 00:31:09.200
other people we've had on the security

00:31:09.200 --> 00:31:12.120
breach podcast you almost have to borrow

00:31:12.120 --> 00:31:13.360
a Terminator reference you can almost

00:31:13.360 --> 00:31:14.880
see Judgment Day coming a little bit

00:31:14.880 --> 00:31:16.320
with a lot of the quantum encryption

00:31:16.320 --> 00:31:18.440
challenges that are out there I just got

00:31:18.440 --> 00:31:20.840
to ask I mean how do you sleep at night

00:31:20.840 --> 00:31:22.600
how how are you how do you feel a sense

00:31:22.600 --> 00:31:23.960
of calm about things from a cyber

00:31:23.960 --> 00:31:26.120
security perspective knowing how quickly

00:31:26.120 --> 00:31:29.320
the bad guys can evolve adapt to things

00:31:29.320 --> 00:31:31.039
yeah I mean I I'll answer that Jeff Paul

00:31:31.039 --> 00:31:32.559
will have his answer but honestly I

00:31:32.559 --> 00:31:34.799
don't sleep that well at night um you

00:31:34.799 --> 00:31:38.039
know I uh and and AI scares the heck out

00:31:38.039 --> 00:31:40.720
of me it really does because you know it

00:31:40.720 --> 00:31:43.960
took no time again for those guys to

00:31:43.960 --> 00:31:46.720
develop their own GPT the worm

00:31:46.720 --> 00:31:49.880
GPT um and you know all we can do is

00:31:49.880 --> 00:31:52.120
what we can do and and we just you know

00:31:52.120 --> 00:31:54.799
if I had it in my way this nation would

00:31:54.799 --> 00:31:57.440
be covered in postquantum cyber all

00:31:57.440 --> 00:32:00.159
across every channel um and and that

00:32:00.159 --> 00:32:01.960
would give us the best chance so in

00:32:01.960 --> 00:32:04.639
essence we're behind the curve and uh

00:32:04.639 --> 00:32:06.600
you know China just announced the the

00:32:06.600 --> 00:32:08.279
fast world's fastest quantum computer by

00:32:08.279 --> 00:32:09.639
the way as well so they're they're

00:32:09.639 --> 00:32:11.279
moving into Quantum you know and they

00:32:11.279 --> 00:32:13.799
they may have surpassed Us in in what we

00:32:13.799 --> 00:32:17.360
and call you know Quantum Supremacy but

00:32:17.360 --> 00:32:21.720
uh we need to just keep at it so it's

00:32:21.720 --> 00:32:23.679
it's our nation it's our future as Paul

00:32:23.679 --> 00:32:26.240
said this is you know what's at stake

00:32:26.240 --> 00:32:28.559
for our kids and Grand kids and we

00:32:28.559 --> 00:32:31.240
either get this right or it's a global

00:32:31.240 --> 00:32:33.120
difference this is an existential

00:32:33.120 --> 00:32:36.200
problem and so yeah I don't sleep we

00:32:36.200 --> 00:32:39.200
just keep at it and we go 247 and we we

00:32:39.200 --> 00:32:41.399
scream from the top of the mountains uh

00:32:41.399 --> 00:32:43.480
you know please start looking at this

00:32:43.480 --> 00:32:46.039
folks get your stuff upgraded um you'll

00:32:46.039 --> 00:32:48.320
be just then then we'll sleep better at

00:32:48.320 --> 00:32:50.320
night yeah if you guys all upgrade I'll

00:32:50.320 --> 00:32:52.399
sleep a lot

00:32:52.399 --> 00:32:55.760
better I I uh I'd counter skip with a

00:32:55.760 --> 00:32:57.120
little bit of I'm maybe a little more

00:32:57.120 --> 00:32:58.480
The Optimist maybe that's why we make a

00:32:58.480 --> 00:33:01.159
good team uh he he's nervous for the

00:33:01.159 --> 00:33:04.000
future but I'm I'm optimistic because I

00:33:04.000 --> 00:33:07.840
believe that if we can together as as a

00:33:07.840 --> 00:33:09.519
country and I know that sounds a little

00:33:09.519 --> 00:33:11.880
hyperbolic uh We've we've faced large

00:33:11.880 --> 00:33:13.880
challenges in the past and if we can

00:33:13.880 --> 00:33:15.600
gather our resources and make people

00:33:15.600 --> 00:33:18.960
aware of this we have such a wonderful

00:33:18.960 --> 00:33:21.840
uh Community Society country that we

00:33:21.840 --> 00:33:23.760
live in that if we can Garner the

00:33:23.760 --> 00:33:25.840
resources and the will to do it and I

00:33:25.840 --> 00:33:28.159
think we can that I think that the

00:33:28.159 --> 00:33:31.039
future does look bright so um as much as

00:33:31.039 --> 00:33:33.600
there is a lot to work on out there I I

00:33:33.600 --> 00:33:35.559
just look at the Spirit of what uh

00:33:35.559 --> 00:33:37.080
America has done in its sense of

00:33:37.080 --> 00:33:39.360
innovation and and and revolutionizing

00:33:39.360 --> 00:33:41.279
things and and getting there and maybe

00:33:41.279 --> 00:33:43.880
we aren't there as fast as we need to be

00:33:43.880 --> 00:33:46.559
but we will get there uh if we all just

00:33:46.559 --> 00:33:48.240
put our our you know shoulder to the

00:33:48.240 --> 00:33:49.919
grindstone and and keep pushing hard and

00:33:49.919 --> 00:33:51.320
that's what we're trying to do every day

00:33:51.320 --> 00:33:53.679
here and it's it's it's important work

00:33:53.679 --> 00:33:55.039
and I think that that sense of

00:33:55.039 --> 00:33:56.919
importance is what drives us uh whether

00:33:56.919 --> 00:33:58.240
whether it be if we're optimistic or if

00:33:58.240 --> 00:34:00.559
we're nervous we do know that that that

00:34:00.559 --> 00:34:02.320
it's so important that we're working

00:34:02.320 --> 00:34:03.639
together in that same

00:34:03.639 --> 00:34:06.080
cause skipp and Paul thanks so much for

00:34:06.080 --> 00:34:07.679
joining us today and to learn more about

00:34:07.679 --> 00:34:10.200
ccure you can check them out at qc.com

00:34:10.200 --> 00:34:13.440
that's Q

00:34:13.440 --> 00:34:15.760
c.com and thanks to you for joining us

00:34:15.760 --> 00:34:17.800
today to catch up on past episodes you

00:34:17.800 --> 00:34:19.720
can go to manufacturing.net

00:34:19.720 --> 00:34:23.560
i.com or mbtm mag.com you can also check

00:34:23.560 --> 00:34:24.879
security breach out wherever you get

00:34:24.879 --> 00:34:27.359
your podcast including Apple am Amazon

00:34:27.359 --> 00:34:29.159
and overcast and if you have a cyber

00:34:29.159 --> 00:34:30.800
security story or topic that you'd like

00:34:30.800 --> 00:34:32.639
to have us explore on security breach

00:34:32.639 --> 00:34:35.200
you can reach me at Jeff

00:34:35.200 --> 00:34:38.240
i.com for skon area and Paul fugner I'm

00:34:38.240 --> 00:34:54.040
Jeff ranky and this is security

00:34:54.040 --> 00:34:57.040
breach

  • Security Bre... jdb10987
    • Re: Sec... Undescribed Horrific Abuse, One Victim & Survivor of Many

Reply via email to