►
From YouTube: Red Hat Enterprise Linux Presents 23: Overcoming Security Vulnerabilities with Red Hat Insights
Description
Security vulnerabilities often show up at the worst of times and demand an all-stop to identify, remediate and test a fleet of systems before they can be compromised. However, with Red Hat Insights, this process does not have to be quite so stressful or time-consuming! Join Eric The IT Guy and John Spinks as they discuss how the Insights Vulnerability Service can help you protect your Red Hat Enterprise Linux servers!
Red Hat Livestreaming: https://red.ht/livestream
Join our Discord! https://discord.gg/PsAT8WG7
Get Started with RHEL: https://redhat.com/tryrhel
Eric The IT Guy Hendricks: Twitter @itguyeric
John Spinks, Senior Principal Technical Marketing Manager : twitter @JBSpinks
Insights: https://console.redhat.com/insights/
Insights Documentation: https://access.redhat.com/documentation/en-us/red_hat_insights/2021
Blog: Red Hat Insights and the delivery of a new security recommendation https://www.redhat.com/en/blog/red-hat-insights-and-delivery-new-security-recommendation
#linux #security
A
A
A
So
if,
if
you're,
if
you're
wanting
to
become
a
systems
administrator
and
think
that
you
have
to
learn
all
the
things
before
you
can
do
so
yeah
you
you'll,
just
if,
if
that's
how
you
approach
things,
you'll
just
never
be
ready
and
john.
I
I
see
you
smirking,
because
I
I
take
it.
You
know
this
to
be
true,
so
why
don't?
Why?
Don't
you
introduce
yourself
and
we'll
get
into
it?
Yeah.
B
Figuring
it
out
is
pretty
much
the
the
mantra
of
any
sys
admin.
Thank
you.
Oh
hey
we're
going
to
get
this
brand
new
product
in
and
just
got
to
figure
out
how
to
use
that
hi
everybody.
My
name
is
john
spinks.
I
am
a
technical
marketing
manager
for
red
hat
insights,
which
is
one
of
the
key
things
that
we're
going
to
be
talking
about
today.
My
background
is
also
as
a
sys
admin.
B
So,
even
though
I
have
marketing
in
the
title,
I
spent
quite
a
bit
of
my
career
as
a
system
administrator
for
linux
windows.
San
hardware
email,
a
variety
of
different
things,
the
smaller
the
shop,
the
more
hats
you
wear
and
I'm
very
familiar
with
that
mantra
of
here's
new
stuff
figure
out
how
it
works.
Now,.
B
So
one
of
the
things
while
he's
struggling
for
the
audio
button,
I
mentioned
that
I'm
the
marketing
rep
for
red
hat
insights
insights
is
a
product
that
we've
got.
That
is
part
of
existing
red
hat
subscriptions
that
you
already
have
today.
It's
included
now
as
part
of
your
red
hat
enterprise.
Linux
subscription,
as
well
as
your
red
hat,
open
shift
and
your
red
hat
ansible
automation
platform
subscription.
A
Learning
as
we
go,
that's
that's
kind
of
the
theme
of
this
show
and
and
has
been
since
it
started
so
so
today,
john
you're,
actually
a
recurring
guest
on
the
show,
and
we
and
you
kind
of
did
a
quick
overview
there.
While
I
was
reconnecting
everything
of
what
insights
is.
Did
you
happen
to
mention
just
how
many
different
services
are
live
with
within
sites
right
now?
I.
B
Did
not
because
that's
a
it's
a
bit
of
a
loaded
question.
I
don't
have
an
exact
number,
I
let's
do
it.
Let's
do
it
live
because
that's
the
way
we
like
to
do
things.
Insight
started
out
as
the
advisor
service
used
to
be
that
that's
all
that
there
was
within
insights,
so
advisor,
and
then
we
introduced
the
vulnerability,
the
compliance
and
the
system
comparison,
which
is
now
known
as
drift
service.
There's
also
policies
patch
subscriptions
and
we
are
coming
out
very
shortly.
We
have
in
beta
a
resource,
optimization
service.
B
We
also
have
a
couple
services
that
are
in
private
beta,
so
we're
somewhere
between
10
and
12,
depending
on
how
you
count
them.
We
also
sometimes
refer
to
our
inventory
service
and
our
remediation
service,
and
then
the
entire
platform
has
capabilities
like
our
back
notifications,
and
these
are
all
part
of
what
you
get
in
the
box
as
well.
Those
are
just
on
the
rel
side.
I
did
mention
that
insight
supports
other
platforms.
B
A
I
would
have
loved
to
have
had
a
tool
like
this,
because
it's
like
having
a
systems
administrator
who's,
always
on
call
who
never
calls
in
sick
just
constantly
out
there
checking
on
on
the
health
and
and
the
performance
of
of
of
your
your
your
entire
fleet
of
started
off
with
rel
servers,
and
then
you
know,
as
you
mentioned,
expanded
to
ansible
and
open
shift.
So
I
mean
this.
A
This
platform
has
just
grown
exponentially,
just
every
single
release
or
every
quarter,
or
so
it
seems
like
there's,
there's
new
services
or
new
features
coming
online.
So
I
would
imagine
john
not
we're
not
trying
to
sell
anything,
but
just
for
those
out
there
going.
We
should
look
at
this.
I
imagine
something
as
powerful
as
insights
would
be
really
expensive.
B
Again,
it's
included
with
part
of
your
existing
rail
subscriptions,
so
it's
something
that
you
already
have
today.
All
we
want
you
to
do
is
enable
it
turn
it
on
and
see
some
of
the
value,
because
it
is
part
of
that
value
of
subscription
and
the
reason
that
we
we
talk
about
it.
That
way
is
part
of
what
you
pay
for
a
subscription
for
is
support.
B
Insights
was
originally
created
with
that
advisor
service
and
the
whole
goal
of
that
advisor
service
is,
let's
tell
you
about
things
that
might
happen
to
your
environment
before
they
happen.
Let's
give
you
some
proactive
guidance,
some
analytics
of
your
environment,
so
you
don't
have
to
call
red
hat
at
three
o'clock
in
the
morning
when
your
beeper
goes
off.
It's
been
a
long
time
since
I've
had
a
beep,
unfortunately,
but
you
know
email
whatever
you
want
to
call
it.
B
You
get
that
ding
or
that
call
from
your
boss
wakes
you
up
in
the
middle
of
the
night.
Oh
what
now,
rather
than
having
to
deal
with
that,
if
you
can
proactively
know.
Oh,
I
have
this
version
of
the
rail
kernel
and
I
have
that
version
of
a
certain
package
and
with
that
particular
combination,
if
it
runs
more
than
120
days,
you
have
a
kernel,
panic,
oops.
B
B
So
if
you're
about
to
encounter
one
of
these
issues,
we
say
hey,
this
is
coming
hey.
This
is
coming
quick.
You
might
want
to
fix
this
really
fast
with
the
idea
of
we're
going
to
let
you
know
about
it
before
it
impacts
your
systems,
giving
you
an
opportunity
to
to
resolve
the
issue,
and
it
could
be
something
you
know-
maybe
not
that
dire.
But
we
had
a
one
of
the
technical
account.
Managers
or
tams.
Tell
me
a
story
that
he
was
showing
insights
to
one
of
his
customers
and
the
customer.
B
Would
I
think
your
thing
is
broken.
It's
telling
me
that
network
bonding
is
incorrectly
configured
and
we
don't
use
network
bonding.
So
that's
not
a
real
thing.
You
got
a
false
positive
here.
Well,
let's,
let's
dig
a
bit
further
because
you
know
that's,
it's
essentially
a
you
know
an
analysis
engine,
that's
looking
at
the
configuration
of
your
system
and
saying
hey
here's
things
that
we've
discovered.
So
it's
it's
trip
this
for
a
reason.
B
What's
that
reason
and
come
to
find
out,
one
of
the
admins
had
mistyped
an
nm
cli
command
and
partially
enabled
network
bonding
on
a
box.
They
never
would
have
known
about
it.
Otherwise,
it's
just
like
we.
We
don't
use
this
thing.
What
happened,
but
you
know,
fat
fingers
are
a
real
thing
in
the
sysadmin
world.
A
Right
so
we
we
we
kind
of
in
a
previous
episode.
We
you
and
scott
and
chris
kind
of
talked
about
insights
in
general,
but
we
wanted
to
focus
in
on
the
security
vulnerability
piece.
I
mean
every
single
day.
It
seems
like
there's
new
new
attacks,
new
new,
very
public
attacks.
I
mean
there
was
there's
what
the
facebook
thing
a
couple
of
weeks
ago,
there
was
twitch
before
that
I
mean
there's
just
there's
been
pipeline
attacks,
there's
been
upstream
software
supply
chain
attacks.
A
I
mean
it's
just
one
thing
after
another
after
another,
and
so
this
is
definitely
something
that
was
top
of
mind
before
2021,
but
it
seems
like
I
mean,
maybe
you
maybe
your
feeling
has
been
different,
but
it
feels
like
in
2021,
we've
had
more
attacks,
more
public,
very
public
attacks,
things
that
have
hit
not
just
I.t
news
spaces,
but
the
mainstream
news
as
well.
Then
I
think
we've
had
since
I
started
working
in
technology.
B
Yeah,
it's
security
is
definitely
one
of
the
things
that
brings
people
to
insights
pretty
frequently,
I
think
the
most
recent
one
that's
top
of
mind
for
me-
is
microsoft
recently
had
their
open
management
infrastructure
issue
that
came
across,
and
some
of
you
may
have
heard
of
this
already,
but
it
it's
running
systems.
In
azure
there
was
a
omi
package
that
had
a
remote
cold
code
vulnerability.
B
This
is
not
a
red
hat
thing.
This
was
a
microsoft
and
azure
thing,
so
this
is
something
that
popped
up
potentially
very
problematic.
There
was
packages
being
installed
on
a
box
that
you
know
any
azure
box
that
wasn't
really
something
that
the
admin
installed
or
anybody
purposely
installed.
It's
just
part
of
running
your
systems
and
azure.
It
was
there,
and
that
was
actually
a
really
interesting
one
for
the
insights
team,
because
we
found
out
about
this
vulnerability
pretty
much
at
the
same
time
as
everybody
else.
B
B
If
this
particular
issue
was
present,
I
mean
it's,
not
super
hard
I'd
say
is:
do
you
have
a
certain
package
and
you
have
a
certain
version
of
the
package
that
is
vulnerable
and
then
we
created
within
the
advisor
service
one
of
the
the
services
of
insights
that
speaking
about
earlier,
it
runs
on
recommendations
and
it's
essentially
a
rules-based
engine.
I
think
of
it
as
an
if
this
than
that
kind
of
engine
just
to
make.
A
B
Really
simple
and
we
were
able
to
say,
hey
well,
you
know
if
this
is
present,
then
that's
an
issue
like
it's
a
it's
a
potentially
a
vulnerable
package
and
we
should
have
an
alert,
but
just
because
it's
there
doesn't
mean
you're
exposed
right,
but
is
it
running
okay?
If
it's
running
that's
a
different
level
of
criticality?
B
Is
it
communicating
over
a
port?
Is
that
port,
internal
or
external?
If
it's
internal,
it's
still
critical,
still
super
important,
but
if
it's
an
external
port
that
is
communicating,
that's
where
the
real
risk
is
so
we
actually
looked
at
these
different
factors
and
created
recommendations
inside
of
insights.
That
says
you
know
that
looks
at
those
different
conditions.
I
think
there's
five
total
and
we
said
hey:
let's
go
look
for
the
presence
of
this
package.
If
it's
not
there,
no
biggie,
we
don't
trip
the
rule.
B
B
At
that
time
we
didn't
have
a
remediation
in
place,
but
we
were
able
to
let
you
know
about
your
exposure
and
that's
one
of
the
things
that
you
get
that
call
about
at
three
o'clock
in
the
morning.
Oh
my
god,
I
heard
about
this
thing
on
the
news.
Are
we
exposed
okay,
boss?
Let
me
check
and
without
something
like
insights,
you're
taking
the
time
you're
logging
onto
each
box
individually,
that's
running
in
this
particular
situation,
so
in
this
case
it'd
be
running
on
azure
and
you're
checking.
Is
this
package
installed?
B
Okay,
it's
not
there.
Okay,
it
is
on
this
one.
Let
me
write
that
down
rather
than
having
to
go
through.
All
of
that,
you
click
a
link
and
you
go
into
insights
and
you
say:
oh,
am
I
exposed
no,
I'm
good
or
yeah.
I
am
and
there's
three
boxes
or
30
boxes
or
whatever
the
number
is.
We
have
a
public
blog
article
on
that
as
well.
I
think
I've
sent
you
the
link,
it's
it's
not
what
the
rest
of
the
show
links.
B
For
you,
but
if
that's
one
that
you
can
grab,
you
can
throw
it
in
there,
but
there
I
put
about
a
blog
about
that.
A
vulnerability
can
happen
to
anybody.
It
is
not.
I
mean
it's
not
something
that
was
maliciously
done
on
the
part
of
microsoft.
Who
is
our
partner
and
they're
a
great
business
partner?
In
the
creation
of
this
blog?
B
I
actually
talked
to
azure
product
managers
and
marketing
people
from
microsoft,
and
let
them
know
that
this
blog
was
coming
because,
like
hey
like
we
don't
want
you
caught
off
guard
like
we're,
not
microsoft
going.
You
know,
you
did
a
bad
thing
and-
and
we
want
to
let
our
customers
know
you
did
a
bad
thing.
We
said
hey,
you
know,
stuff
happens.
Security
breaches
are,
unfortunately
a
reality
of
life.
A
Well,
and
what
was
really
impressive
about
that
particular
situation
was
the
partnership
kind
of
in
in
action.
It's
one
thing
to
say:
yeah
we're
business
partner,
but
it's
another
thing
for
our
engineering
teams
and
their
engineering
teams
and
even
the
community
to
be
working
together
to
say,
here's
an
issue:
let's
fix
it,
let's
get
it
in
this
tool
that
helps
our
customers.
Our
mutual
customers
identify
that
this
issue
is
there,
so
that
was
the
first.
A
That
was
the
first
thing
that
really
shocked
me
was
just
seeing
that
partnership
that
that
actual
communication
back
and
forth.
The
second
thing
was
the
speed
at
which
this
was
done.
I
mean
it
was
a
couple
of
days.
If
I
remember
the
the
incident
correctly
and
the
issue
was
identified,
a
those
five
criteria
were
defined,
a
fix
was
found
and-
and
it
was
put
up
in
insights
and
and
that
took
that
that
used
to
take
weeks-
and
it
was-
it-
was
definitely.
B
A
big
win
inside
of
red
hat,
like
as
as
a
part
of
a
product
team,
seeing
people
literally
across
the
globe,
like
you
know,
we
found
out
about
this
thing
at
you
know
what
like
4
p.m.
You
know,
and
then
one
of
the
product
managers
who
has
this
thing
is,
is
based
out
of
a
mia
like
he.
He
was
on
calls.
You
know
nine
ten
o'clock
at
night.
His
time
goes
to
bed
wakes
up
the
next
morning
and
they're
like
all
right.
We
got
it.
It's
working,
I
mean
right.
That's
awesome,.
A
B
It
got
the
oh,
my
god.
You
know
that
that's
what
they
ended
up,
naming
it
and
it's
not
part
of
the
cve
other
ones.
You
might
be
a
lot
more
familiar
with.
Are
boot
hole
or
you
know
the
old.
You
know
meltdown
inspector.
If
you
want
to
go
back
a
couple
years,
those
are
ones
that
everybody
was,
you
know,
probably
really
familiar
with.
If
they
had
to
deal
with
it,
you
know
those
get
a
little
bit
more
named
I'll
call
them
celebrity
status,
it's
one!
B
Those
are
the
ones
that
you
get
the
call
about
from
your
boss,
it's
like
what's
going
on
because
it
shows
up
in
a
trade
article
or
it
shows
up
on
the
six
o'clock
news,
but
most
of
them
and
they
happen
pretty
frequently.
It's
just
hey,
there's
a
flaw.
We
need
to
fix
this.
It
gets
associated
with
a
cve
id
and
for
red
hat
it
also
if
it's
something
that
we
can
fix,
because
not
every
one
of
these
can
be
fixed.
B
It's
you
know,
maybe
it's
a
super
old
kernel
version
and
the
fixes
to
go
from
cpu
type
x
to
cpu
type
y.
It's
not
fixed,
that's
a
change
in
architecture,
a
change
in
hardware,
but
if
it's
something
that
can
be
have
a
software
fix,
it
gets
an
errata
associated
with
it.
So
that's
a
you
know,
a
software
patch
or
a
package.
A
Well
and
the
the
scenario
you're
talking
about
happened
to
me,
literally
with
celebrity
status,
vulnerability
called
heartbleed.
So
I
got
the
call
and
it
was
in
the
middle
of
the
night,
but
it
was
it
was
bright
and
early.
You
could
tell
that
someone
high
up
on
the
chain
logged
into
their
into
their
news,
feed
or
over
breakfast
and
went
oh,
my
gosh
are.
A
Are
we
vulnerable
to
this
and
of
course
I
got
the
call,
and
I
got,
I
think
the
company
I
work
for
at
the
time
had
something
like
400
linux
servers
and
there's
three
admins,
and
so
the
400
or
the
the
three
of
us
got
to
divide
up
400
servers
at
like
six
in
the
morning
and
go
through
them
just
a
couple
at
a
time
and
go.
Is
this
here
nope?
This
is
here
nope,
okay
out
to
the
dmz?
Oh,
we
better
fix
this
and.
B
But
in
order
to
help
make
that
experience
better,
one
of
the
things
that
we
built
into
insights
was
our
vulnerability
service,
but
before
we
we
get
into
that,
you
guys
have
been
talking.
You
know,
listen
to
us
talk
for
about
20
minutes.
I
do
want
to
go
ahead
and
share
my
screen
and,
let's
start
actually
looking
at
some
of
this
stuff,
because
that's
going
to
be
a
lot.
B
B
You
get
an
email
notification
or
maybe
you
just
go
out
to
google
and
you
type
in
the
name
of
a
a
security
bulletin
or
a
cve,
and
in
this
case
I'm
just
on
you
know
our
main
security
vol
vulnerabilities
page.
You
can
go
and
browse
these.
You
can
see
the
the
ones
that
are
resolved
or
some
of
them
are
in
progress
here.
So
this
one,
that's
ongoing
that
one
most
likely
doesn't
have
an
errata
associated
with
it
yet
and
I'm
100
guessing
I'm
not
clicking
into
it.
B
B
B
Part
of
it,
as
we
tell
you,
the
impact
at
the
top,
but
I
also
want
to
highlight
a
fairly
recent
changes.
We've
added
in
this
insights
vulnerability
analysis
to
pretty
much
all
of
our
cds.
So
if
you
are
already
a
user
of
insights,
somebody
sends
you
to
a
link
like
this
and
wants
to
know
if
you're
exposed
it's
really
as
easy
as
clicking
view
expose
systems,
and
that's
going
to
redirect
you
to
insights
where
you
can
say
hey
here,
I
am
I'm
already
logged
in.
B
If
I
wasn't
logged
in
you'd
have
to
log
in
it
uses
your
red
hat
account
the
same
one
that
you
would
use
to
see
a
knowledge
base,
entry
or
download
software
or
file
a
support
case.
It's
the
exact
same
account
that
you
would
use
to
access
insights
and
in
this
case
this
particular
kernel
bug
it
happens
to
affect
15
systems
in
my
environment.
B
I
can
see
it
listed
right
here
trying
to
wait
for
my
thing
to
behave,
and
then
I
can
actually
see
every
single
one
of
the
systems
that
impacts
listed
below
it
more
information
about
it.
So
this
is
one
way
that
people
might
come
in
and
find
out
about
a
vulnerability,
so
I'm
gonna
pause
there
eric
and
see.
If
you
got
any
questions
about
that
before
I
move
on.
A
Yeah
so
with
the
cve
database,
I'm
thinking
that
there's
there's
kind
of
a
tiered
system
to
it,
especially
if
you're
using
insights
so
a
question.
Some
of
our
some
of
our
users
may
have
is,
are
cves
exactly
the
same
globally
or
do
certain
vendors
have
certain
changes
that
they
make
to
cves
like
red,
hat's,
now
going
to
track
a
windows
cve,
because
we
don't,
we
don't
have
a
windows
operating
system.
Does
that
question
make
sense
yeah.
B
And
same
same
thing,
kind
of
like
that
microsoft
example
I
gave
is
that
microsoft
cve
it
did
have
a
number
associated
with
it.
I'm
not
going
to
have
that
in
the
red
hat
database,
because
we're
browsing
red
hat
cve,
so
these
are
ones
that
are
specific
just
to
us
as
a
vendor.
So
all
I'm
seeing
in
here
is
is
the
red
hat
stuff.
So
it's
definitely
a
red
hat,
centric
view
of
the
world.
B
A
Does
insight.
Does
insights
give
me
the
ability
to
narrow
that
down
even
further?
So
if
I'm
not,
if
my
systems
don't
use
a
certain
a
certain
package,
can
I
mark
that?
Can
I
set
up
sort
of
my
own
cve
structure
or,
if
there's
something
that
is
critical
to
my
business?
Is
there
a
way
for
me
to
sort
of
internally
say
this
is
really
really
really
important?
It
may
only
be
a
medium
cve,
but
this
is
critical
to
our
business.
So
I'm
going
to
internally
mark
this
as
a
high.
Yes,.
B
And
I'll
come
back
to
that
in
a
moment
because
there's
one
other
thing
I
want
to
highlight
about
the
higher
red
hat
process.
Before
I
delve
a
little
bit
more
into
insights,
we
do
have
and
the
name
has
changed.
We
used
to
call
it
customer
security
and
awareness.
It's
recently
changed.
I
do
not
remember
the
new
name,
I
haven't
got
it
to
memory
yet,
but
there's
actually
a
team
that
goes
to
some
of
these
big
security
vulnerabilities
like
boot,
hole
or
meltdown
inspector.
B
In
fact,
I
don't
remember
what
boot
hole
is
so
give
me
a
second
I'm
gonna
yeah,
that's
fine,
but
anyway
there
there's
a
group
that
will
actually
go
through
and
really
dig
deep
into
some
of
these
really
impactful
vulnerabilities
and
that's
where
this
extra
information
comes
from,
like
these
executive
summaries,
if
it's
associated
with
any
other
cve.
So
you
know
this
one
is
you
know
we're
looking
at
this
vulnerability,
but
then
there's
also
an
associated
vulnerability,
and
so
we're
going
to
give
you
just
a
little
bit
more
information.
B
That's
above
and
beyond.
Just
hey,
there's
a
security
flaw
and
you
should
fix
it.
We're
actually
talking
in
some
depth
here
about
the
different
capabilities,
and
this
is
just
on
the
you
know
right
within
the
customer
portal
site.
So
this
isn't
even
within
insights.
Insights
will
redirect
you
to
this.
So
if
you
happen
to
find
out
that
a
system
is
affected
by
a
certain
vulnerability,
we're
going
to
bounce
you
out
here,
because
they've
put
in
so
much
work
already,
I
mean
I'm
still
scrolling
down
this
page
and
I've
just
got
down
here.
B
You
know
kind
of
towards
the
end.
We
do
have
a
diagnosis,
script,
a
ton
of
references,
but
the
really
really
easy
way
to
detect.
If
you
have
something
like
this,
like
I
said
before,
is
you
just
go
and
click
the
button
and
you
can
see
it
within
insights?
This
does
require
you
to
register
your
systems
to
insights,
and
that
is
a
super
easy
process.
B
There's
ansible
scripts
built
in
for
it
there's
a
rel
system
role.
There's
a
satellite
role
set
up
and
if
you
want
to
do
it
manually,
if
you're
on
rail,
eight,
it's
a
single
command,
insights,
client,
dash
dash
register
and
you're
done.
If
you're
running
an
older
system,
it's
going
to
double
your
work,
you
first
have
to
install
that
package.
So
it's
two
commands
you
have
to.
You
know,
install
the
insights,
client
and
then
you
have
to
register
and
we
actually
walk
you
through
how
to
do
that.
B
There's
a
register
systems,
tab
inside
of
insights,
we'll
walk
you
through
how
to
do
it
and
give
you
both
give
you
the
ansible
playbooks,
if
you
need
it,
but
to
your
point
earlier
you
you
asked
me
if
I
have
a
vulnerability
like
this,
and
it
says
it's
important
but
you're
like
no.
No
for
us,
it's
critical
or,
conversely,
if
you're
like
eh,
you
don't
care
you,
we
do
give
you
the
flexibility.
B
If
you
look
here
kind
of
towards
the
right,
there's
a
business
risk
and
a
status
that
allows
some
additional
capabilities
and
if
you're
already
familiar
well,
I
got
it
highlighted
if
you're
already
familiar
with
a
common
vulnerability,
scoring
system
or
cvss.
We
show
you
what
the
css
base
court
is
in
here.
This
one's.
You
know
it's
a
3.0.
B
Oh
sorry,
it's
a
7.0
is
a
score
and
that's
compiled
from
a
lot
of
different
vectors,
and
we
summarize
them
here
for
you,
but
if
you're
new
to
this,
you
might
not
know
that
av
is
attack
vector
if
you
need
to
know
that
stuff,
you
click
the
little
question
mark
and
it's
going
to
give
you
all
that
information
and
it's
essentially
summarizing
from
our
database.
What
the
metrics
are
that
make
up
the
common
vulnerability
scoring
system
and
why
it's
been
scored
the
way.
It
is
well
nice
to
your
point.
B
A
B
Always
a
great
reason
to
say
that
business
risk
is
high,
that's
actually
going
to
show
up
in
reports
and
stuff
going
forward,
so
you
might
want
to
watch
that.
Maybe
you
don't
put
something
too
snarky
in
there,
but
you
know:
we've
got
a
business
first,
that's
associated
with
it
now
and
you
know,
like
I
said
I
set
it
as
high.
Conversely,
you
could
put
it
as
low
the
other
import
part
of
that
is
the
status.
You
actually
have
to
walk
this
generally
through
a
remediation
status.
B
So
once
you
know
this
vulnerability
is
here,
have
you
reviewed
it?
Maybe
if
not,
you
move
it
to
in
review,
and
you
say:
okay,
we're
going
to
start
taking
a
look
at
us
to
see.
If
we
need
to
do
it,
your
other
options
are
on
hold
like
hey,
we
need
more
information
or
we've
got
to
go
to
another
internal
stakeholder
and
get
more
information
about
you
know
is:
what's
the
criticality
of
this
all
right,
we
have
decided,
we
need
to
fix
it.
Then
we
schedule
it
for
a
patch
once
we
schedule
it
for
a
patch.
B
We
can
go
ahead
and
say
it's
resolved.
We're
done
we
fixed
this
issue.
It's
over
insights
will
also
be
updated
when
there's
no
more
systems
that
are
hitting
it
and
then
the
other
options
are
no
action.
We've
just
accepted
that
this
is
a
risk.
We're
going
to
take
we're
not
worried
about
this
particular
cve
or
you've
resolved
it
via
some
other
mitigation.
So
you've
got
these
different
options
and
you
can
set
this
either
at
the
cve
level
or
you
could
set
it
at
individual
system
level.
B
So
if
you've
got
a
set
of
systems
that
are
maybe
their
development
system,
so
you're
not
as
worried
about
certain
vulnerabilities,
you
can
say
hey
for
these
systems.
It's
okay
we're
going
to
accept
the
risk
on
these,
but
for
the
production
systems
we
got
to
fix
it.
So
once
you
set
your
status,
it's
now
updated
it's
in
review
and
we
can
go
ahead
to
the
process
of
reviewing
all
of
this.
B
So
I've
kind
of
jumped
the
gun
here,
a
little
bit
when
we
were
talking
about
because
we
went
in
the
way
that
a
you
know
if
you're
going
from
the
customer
portal
you
might
go
in,
but
I
actually
want
to
take
a
step
back
and
I
want
to
show
insights
at
a
higher
level.
You
cool
with
that
yeah.
Let's
do
it
all
right,
so
I
just
switched
tabs.
If
you
notice
I'm
here
at
console.redhat.com,
you
can
also
get
there
from
typing
cloud.redhat.com
and
logging
in,
and
this
is
that
home
page.
B
At
any
point
within
this,
if
you
want
to
see
what's
coming,
you
can
actually
use
the
beta
release.
You
can
see
stuff,
that's
coming
soon.
It's
not
quite
released,
yet
we
plug
this
in
for
everybody.
It
might
not
have
all
the
features.
It
might
look
a
little
off
because
it
is
in
beta,
but
you
should
have
noticed
when
I
made
that
switch
gave
me
a
little
bit
of
a
visual
look
and
feel
I've
now
got
a
summary
here
of
rel,
where
I
can
see
some
incidents.
B
B
B
B
If
I
go
back
to
this
dashboard,
there's
a
lot
of
information
here.
If
you're
new
to
this,
it
can
almost
be
overwhelming,
because
I've
got
all
these
different
services.
The
names
of
the
services
are
on
the
left.
I
mentioned
some
of
them
earlier.
They
all
have
different
capabilities
and
they
bring
you
different
value
and
every
one
of
them
is
included
again
as
part
of
your
redhead
enterprise
linux
subscription.
So
there's
nothing
to
buy
here.
You
just
gotta
turn
it
on
the
one
we're
focusing
on
is
the
vulnerability
system.
B
B
A
So,
in
other
words,
with
a
known
exploit
that
means
somebody
has
actually
executed
this
in
the
wild
someone
has
reported.
Yes,
this
has
happened
to
me
as
opposed
to
a
lot
of
cves.
Are
I
don't
want
to
say
experimental,
but
I
guess
theoretically
possible
so
with
a
with
a
known
exploit,
this
means
it's.
It's
actually
happened.
Someone
has
compromised
my
system
using
this.
This
particular
cve.
A
B
Not
under
a
harvest
moon
in
the
third
month
of
the
year
on
the
day
that
ends
with
q,
you
know
this
is
actually
something
that
there's
known
exploits
out
there
in
the
wild
that
people
could
potentially
be
taking
advantage
of.
So
but
it's
very
important,
you
don't
confuse
that
with
you.
Yourself
have
been
exposed,
but
it
is
important
to
know
that
these
potentially
have
a
higher
level
of
criticality,
because
people
have
you
know,
take
taken
advantage
of
these
somewhere
in
the
world
and
we
can
also
see
by
a
cvss
score.
B
B
I
can
also
go
on
the
vulnerability
side.
I'm
in
the
left
hand,
tab
now
just
to
make
sure
you're,
following
along
with
my
mouse,
I've
expanded
this
cves
reports
or
systems.
So
I
can
view
this
by
cve.
I
can
view
this
by
system
and
I
can
also
view
you
know
create
my
own
report
if
I
want
to
out
of
this
vulnerability
service.
So
if
I
start
by
going
into
that
cve
view,
this
is
the
boss
calling
you
saying,
hey.
B
I
heard
about
this
thing
on
the
news
I
heard
about
boot
hall
type
in
boot,
hall.
Okay,
there
it
is
it's
cve
2020,
107
13.,
it
has
a
security
rule
associated.
I
have
four
systems
exposed
to
this.
Oh
crap.
Maybe
I
need
to
fix
this,
so
I
can
go
into
the
vulnerability
itself.
I
can
see
again.
Some
of
the
information
from
these
security
rules
is
a
link
to
my
database
and
if
I
want
to
know
that
these
are
my
four
systems
that
are
exposed-
click
the
box
there
they
are.
B
I
can
export
this
out
to
a
csv
or
a
json,
so
you
know
boss
calls
up
with
a
phone
call
saying
I
need
to
know
every
system
that's
affected
by
this
particular
vulnerability.
Now
and
json
file
done.
You
know
here
you
go
boss.
You
know
I
have
that
in
your
email
in
two
minutes
it
doesn't
take
any
time
at
all
to
do
and
it
really
helps.
You
know
what
your
security
posture
is
inside
your
environment.
A
B
B
So
we
wanted
to
do
it
that
way
and
that
that's
what
they
did
and
in
almost
every
case
you
know,
insights
came
in
far
ahead
and
I
think
the
only
place
it
lost
was
our
policy
service
and
that
included
it
lost
only
a
number
of
steps
and
that
included
steps
like
build
a
new
policy
from
scratch
and
opt
into
email
alerts.
So
I
could
potentially
argue
that
that
one
should
have
a
lesser
number
of
steps,
but
like
eh,
I
take
I'll
take
one
if
we
went
on
the
other
ten.
A
Well,
having
been
on
the
on
the
receiving
end
of
a
security
vulnerability
report,
you
bring
in
some
third
party,
they
they
do
a
multi-day
audit
process,
there's
usually
some
black
box
script
that
they're
like
here
log
in
to
all
of
your
systems
as
root
and
run.
This
thing
I
think,
you're
not
yeah,
and
then
they
go
well.
A
I
have
no
idea
what
any
of
this
means,
and
so
then
you
just
you-
have
to
manually
start
grouping
grouping
systems
together.
You
get
really
good
with
the
whole
filtering
system
in
in
your
spread
spreadsheet
tool,
it's
like
sorted
by
environments
sorted
by
system
sorted
by
severity
and
whatever
shows
up
on
the
top
screen
of
this
spreadsheet.
That's
what
we'll
focus
on
this
quarter,
because
by
then
they'll
come
back
and
there'll
be
a
whole
new
set
of
vulnerabilities
and
and
then
we
get
to
look
at
you
know
another
million
cell
spreadsheet
that
actually
has
crashed.
B
B
One
of
the
things
I
want
to
highlight,
I
think
I
showed
when
I
was
on
the
dashboard
I
had.
I
think
the
number
was
17
systems
registered,
so
I
mean
it's
not
a
ton
of
systems
and
I
purposefully
have
old,
outdated
systems
in
this
environment,
because
part
of
my
job
is
to
show
you
this
stuff,
so
for
anybody
watching
yeah,
I'm
not
just
a
horrible
system
admin!
I'm
doing
this
on
purpose,
because
I
want
to
show
some
of
these
issues.
B
So
across
these
17
systems,
I've
got
over
a
thousand
cves
that
impact
that
entire
pool
of
systems,
the
default
filter
that
we
show
inside
of
insights,
you'll
notice
it
right
here
above
my
mouse
systems,
exposed
one
or
more.
We
have
this
turned
on
by
default,
because
we
want
to
show
you
systems
that
are
impacted
by
a
cve.
B
I'm
only
showing
you
the
thousand
or
so
that
impact
me,
and
I
can
turn
that
filter
right
back
on,
there's
actually
a
bunch
of
other
filters
in
here
as
well.
So
if
I
want
to
know
only
about
those
systems
with
known
exploits,
it's
very
easy
for
me
to
turn
that
filter
on
I've
got
nine
of
them.
I
can
see
what
they
all
are
right
here
again.
I
can
export
that
out
to
a
list.
B
The
lists
are
their
wysiwyg
and
what
you
see
is
what
you
get
so
if
I've
got
this
filtered
in
a
certain
way,
and
I
export
it
out-
that's
what
it's
going
to
show
me.
It's
exactly
what
I
have
here
on
the
screen,
and
I
can
also
do
it
by
you
know
certain
base
scores.
If
I
really
only
want
to
know
about
a
range
between,
I
only
care
about
things
between
seven
and
ten.
There
you
go
done.
You
know
it's,
it's
pretty
easy
to
go
ahead
and
click
enter.
B
Sometimes
yeah
picky-
oh,
if
that's
the
worst
thing
that
happens
in
a
demo,
I'll
be
happy
yeah,
but
yeah.
All
of
this
information
is
here
and
it's
filterable,
it's
just
not
a
it's,
not
a
major
it
is
there
might
so.
There
are
cvss
based
scores
down
at
the
bottom,
so
I
got
you
know
clear
clearing
the
exposed.
I've
got
over
two
thousand,
so
yeah,
it's
a
pretty
it's
a
pretty
neat
little
tool,
but
one
of
the
the
next
steps
is
once
you
identify
that
you
have
a
vulnerability
with
them.
B
B
I
can
actually
go
through
the
remediation
process
right
here.
So
if
your
boss
wants
to
know
not
only
what
systems
are
impacted,
but
what
does
it
take
to
fix
them?
We
can
actually
go
through
the
process
and
I'm
going
to
pick
a
couple
of
my
my
systems
that
are
connected
here
to
a
satellite.
This
801
802,
I'm
going
to
click
remediate
and
what
this
is
going
to
do
for
me
is.
B
Fix
stuff
playbook,
I'm
going
to
create
a
playbook;
it's
just
got
these
two
systems
and
I
can
add
other
actions
to
this.
So
I
can
fix
multiple
things
in
a
playbook.
I
can
have
every
system
involved.
All
I'm
doing
right
now
is
generating
a
playbook
to
handle
this
particular
action,
which
is
just
upgrade
the
associated
packages
associated.
You
know
with
the
cve.
It
does
tell
me
that
it
needs
a
reboot,
so
reboot
required
is
yes.
I
can
turn
off
that
auto
reboot
in
the
playbook.
B
If
I
want
to
I'm
not
actually
taking
any
action
right
now
other
than
creating
the
playbook,
so
I
click
submit
I'm
going
to
click,
my
open
playbook
fix
stuff
and
that's
going
to
redirect
me
to
the
remediation
service.
So
if
I
look,
at
my
left
hand,
nav
bar
there,
I'm
now
in
the
remediation
section-
and
this
has
got
again-
there's
my
cve-
that's
the
only
thing
I
have
in
here
right
now:
it's
associated
with
two
different
systems-
rail801
and
rail802,
and
I'm
able
to
download
this
playbook.
B
B
So
technical,
so
my
two
hosts-
and
we
actually
have
there's
a
signature
here,
so
if
we
are
actually
going
to
run
this
playbook
I'll
talk
more
about
that
in
a
moment,
we've
got
a
signature
to
you
know
letting
us
know
that
there's
been
no
tampering
with
this
particular
playbook.
We're
gonna
check
for
our
update,
we're
gonna
update
our
packages,
reboot
the
system
if
it's
needed
and
then
we're
going
to
rerun
insights,
which
will
make
sure
that
it's
clear
so
at
the
end
of
this
you
know
this
is
everything
that's
in
the
playbook.
B
I
can
see
anything
that
insights
wants
to
do
right
here.
If
I
want
to
manipulate
this
playbook
and
run
it
through
an
automation,
controller
or
formerly
known
as
ansible
tower,
you
can
do
so
fully
support
it
or
you
have
whatever
method
you
use
to
run.
Ansible
totally
cool.
We've
got
that
playbook.
We
generate
that
for
you
and
we
make
it
super
simple
to
fix
the
stuff
that
insights
finds
just
by
downloading
the
playbook,
I'm
going
to
pause
there
before
I
talk
about
the
next
step
of
it,
so
that
seems
super
handy.
A
So
what
you're
telling
me
is
not
only
will
insights
with
the
vulnerability
service,
bring
all
the
cves
to
the
surface,
so
I
can
prioritize
and
and
see
exactly
what
what
piece
of
my
enterprise
is
is
affected,
but
now
you're
telling
me
that
from
the
same
console
I
can
fix
all
of
those
issues
in
one
swoop.
If
I
were
crazy,
yep.
B
B
Is
the
next
step
is
execute
playbook,
that's
a
little
bit
different
thing.
This
is
the
one
part
of
what
I'm
talking
about
today.
That
does
require
something
more
than
just
a
rail
subscription.
This
particular
feature
also
requires
satellite.
So
if
you've
got
a
satellite
you're
good
to
use
this
you've
already
got
everything
you
need.
If
you
don't,
then
what
we're
talking
about
is
a
smart
management
subscription
which
includes
satellite.
B
B
If
you
have
it,
but
you
haven't,
set
it
up,
you'll
get
a
message
kind
of
similar
to
the
one
I
haven't
closed
yet,
which
is
do
more
configure
your
systems
with
cloud
connector
and
that's
a
job.
You
do
inside
your
satellite
itself,
it's
just
an
ansible
playbook
that
you
run
and
it
creates
a
connection
between
insights
and
cloud.redhat.com,
insights
and
satellite.
So
it
just
creates
that
connection
for
you.
What
that
allows
us
to
do
is
click
that
execute
playbook
button.
This
is
telling
me
that
my
two
systems
are
connected
via
my
satellite.
B
That
connection
status
is
ready,
and
if
I
want
to
all
I
got
to
do
is
click
that
execute
playbook
on
two
systems
button.
It
actually
takes
that
playbook.
It
transfers
it
over
to
the
satellite,
the
satellite,
if
you've
got
any
capsules,
is
going
to
transfer
it
over
to
the
appropriate
capsule
and
then
it's
going
to
run
it
with
ansible
remote
execution.
So
it's
going
to
run
this
playbook
for
you,
it's
running
right
here.
It
takes.
You
know
this
particular
one
probably
takes
a
couple
minutes
to
run
and
we
could
actually
even
see
inside
the
ui.
B
A
So
a
use
case
that
that
struck
me,
as
you
were
talking,
was
if
I
have
satellite,
if
I
have
my
redhead
enterprise,
linux
boxes,
my
red
hat
satellite
and
my
vulnerability
service
and
insights
all
interconnected.
I
don't
have
to
leave
this
ui.
Otherwise,
if
we're
done,
if
we're
doing
downloading
playbooks,
I
could
see
using
those
playbooks
and
calling
them
from
kind
of
bootstrapping
them
with
within
maybe
a
maintenance
window
playbook
that
hey
on
saturday.
A
I
want
to
run
we're
going
to
patch
these
servers
using
an
ansible
playbook,
I'm
going
to
remediate
these
issues
by
calling
another
playbook,
and
I
can
actually
just
pre-stage
all
of
this
using
ansible
and
then
oh,
it's
it's
10
o'clock
on
saturday.
I
can
kick
this
off,
kick
off
a
a
playbook
that
calls
other
playbooks
or
or
run
them
kind
of
one.
A
At
a
time,
I,
the
the
best
day
in
my
sis
admin
career,
was
when
I,
when
I
discovered
screen
and
later
tmux,
because
I
could
have
multiple
things
going
on
in
different
places,
but
I
could
I
could
take
these
these
playbooks
and
pre-stage
them
so
that
when
when
a
maintenance
window
does
come
around,
especially
in
the
case
of
like
your
fixed
stuff
playbook,
that
requires
a
reboot.
I
can
have
all
that
stuff
ready
to
go
so
that
I
don't
I'm
not
sitting
there,
the
night
of
of
a
maintenance
window
going
all
right.
A
It's
it's!
It's
now,
one
after
now,
I've
got
to
log
into
this
box.
Let
me
look
at
my
my
spreadsheet
here.
Okay,
so
I've
got
to
run
this
command
and
this
command.
I
just
say,
nope,
kick
off
this
playbook
on
the
system
and
just
wait
for
the
system
to
come
back
up
and
how
long
would
it
take
me
to
be
able
to
go
back
into
into
into
the
vulnerability
screen
and
see
that
that
that
issue
has
been
remediated.
B
Pretty
much
as
soon
as
it
completes
running
the
last
step
of
that
job
is
for
it
to
run
insights
again
and
that
run
of
insights.
It
just
re
analyzes
and
it
takes
a
couple
seconds
at
most
and
it
will
update
that
hey.
This
is
no
longer
a
problem,
so
I
won't
show
you
anymore.
I
think
kind
of
to
your
point.
B
I
went
to
the
remediation
section
here,
so
you
can
see
these
are
all
different,
playbooks
that
I've
created
through
over
the
last
couple
months,
it's
in
the
ansible
documentation
for
ansible,
tower
automation,
controller
that
actually
walks
you
through
how
to
set
up
a
job
on
the
controller
side
that
will
sync
with
this
remediation.
So
you
can
actually
sync
all
of
these
playbooks
you
create
inside
of
insights
over
to
your
towel
or
your
automation,
controller,
and
that's
that's
when
it
gets
really
handy.
A
So,
from
a
high
level
overview
we
can
we
can.
We
can
do
more
research
on
what
cves
are
we
can.
We
can
look
at
specific
cves.
We
can
edit
how
they
look
to
our
own
dashboards.
So
like
this
is
this
we
can
change
the
the
business
priority
so
that
they
get
so
they
get
kind
of
surfaced.
We
look
at
things
like
which
systems
are
but
systems
are
affected.
A
B
We've
got
I.
I
went
back
into
the
playbook
that
we
started
a
moment
ago
and
I
only
did
two
systems.
I
mean
this
is
my
lab
environment.
It's
smaller
like
for
the
purposes
of
you
know
this
conversation
like
I
want
something:
that's
pretty
nimble
happens
pretty
fast,
so
I
didn't
want
to
run
like
20
systems,
but
yeah
I
mean
insights.
It
can
handle
upwards.
B
I
think
we're,
I
think
our
qa
testing
goal
last
I
heard
is
we're
in
the
quarter
million
range
for
like
concurrent
operations
and
things
like
that
like
we,
this
is
built
for
scale,
even
though
I'm
showing
you
two
don't
be
like.
Oh,
this
can
only
handle
two
systems
just
demo
purposes.
We're
trying
to
keep
it
simple
and
easy,
but
really
the
complexity
of
this
is
it's
there's
nothing
to
it.
B
B
It
should
be
that
easy,
like
assuming
that
you're
running
an
environment
out
of
the
box,
like
should
be
just
run,
the
playbook
creates,
creates
the
connection
between
cloud.redhead.com
and
the
satellite
and
you're
done
if
you're,
also
using
a
satellite
anything
that
insights
is
doing
for
its
analysis
that
collection,
it's
all
proxy
to
the
satellite
by
default.
So
you
don't
have
to
worry
about
another
web
proxy
or
a
bunch
of
individual
nodes
reaching
out
to
the
internet,
it's
all
proxy
through
satellite,
and
we
we
should
talk
a
little
bit
about
that
collection
before
we
end.
A
B
Put
a
link
already
in
the
chat.
I
see.
No,
actually
that's
the
insights.
One
we've
got
one
on
the
inside
security
page.
If
you
can
drop
that
one
in
there,
we've
got
a
trust
page
out
there.
Already
it's
publicly
available
that
talks
about
all
of
the
information
that
we
do
with
insights
and
I've
got
it
open
here
on
my
screen
as
well.
B
B
We
do
not
target
any
personally
identifiable
information.
We
don't
want
your
usernames
or
your
passwords.
I
don't
want
any
of
that
stuff.
All
we're
looking
for
is
the
base
information
that
we
need
to
detect
if
these
situations
exist.
So
something
like
that,
oh
my
god,
vulnerability
like
we
need
to
know
if
that
particular
package
is
installed.
What
version
is
that
package?
Is
that
package
running
and
is
it
listing
on
certain
ports?
So
for
that
particular
vulnerability,
we
would
need
to
know
certain
things
for
one.
B
B
All
of
that
information
is
right
here
on
this
page,
and
if
you
want
to
see
what
insights
collects,
we
actually
have
a
one
article
on
system
administrator,
a
system
information
collected
for
insights,
there's
another
one.
Further
down
that
talks
about
how
you
can
obfuscate
your
ip
address
and
host
names.
You
don't
want
to
give
them
to
me.
That's
okay
doesn't
bother
me
a
bit.
I
don't
need
them.
It
does
make
your
life
a
little
bit
easier.
B
If
you
want
to
do
the
remediation
steps,
because
if
you
updo
the
data
upload,
all
we're
going
to
see
is
a
uuid.
If
you've
obfuscated
your
your
host
names,
we
do
let
you
set
a
ansible
host
name
or
a
short
name.
That
makes
it
easier
for
you.
But
if
you
just
hide
everything
at
some
point,
you
make
it
a
little
harder
on
yourself
to
do
the
the
remediation
inside
the
ui.
B
So
if
you've
got
certain
information,
you
want
to
make
sure
never
gets
collected
like
you
have
full
100
control
of
that
and
you
can
generate
a
collection
and
you
can
look
at
it
there
locally.
So
you
can
do
it
without
sending
any
data
to
red
hat
and
be
like
what
does
this
thing
collect
most
of
the
people
that
go
and
inspect.
This
have
absolutely
no
concerns
with
the
information
that
we're
collecting,
because
it
all
makes
sense
and
the
benefits
far
outweigh
the
risk
to
most
people.
A
B
B
We
did
have
one
customer
call
us
to
the
mat
and
say
you've
collected
something
that
we
consider
personally
identifiable
information
and
we
were
like.
Okay
tell
us
more
like
what's
going
on.
Like
you,
you
know
we
have
this.
We
have
this
this
sensitive
name
and
we
see
it
in
the
collection-
and
this
is
very
concerning
to
us
and
we're
like
all
right.
Well,
let's,
let's
dig
in
let's
find
out
what
happened
turns
out
that
a
sis
admin
had
taken
this
project
name
or
company
name.
B
I
don't
remember,
100
what
it
was,
but
they
had
named
a
a
damon
inside
the
box
with
that
name,
and
it
was
running,
and
one
of
the
things
that
we
do
look
at
is
what
our
running
processes,
because
we
need
to
you,
know
we
can
test
and
there's
other
cool
things.
We
can
do
with
the
facts
within
our
drift
service,
and
things
like
that,
so
we
did
collect
the
name
of
a
running
service
and
it
happened
to
be.
It
was
named
this
sensitive
name
and
they
were
like
are
bad.
B
Okay,
we
see
and
then,
but
we
did
show
them
like
hey.
You
have
full
control.
You
can
you
can
cut
this
out
if
you
want
to
make
sure
it's
never
collected
like.
Do
it
put
any
name
in
there
that
you're
worried
about
be
it
your
company
name
or
a
since
you
know
super
secret
project,
name
whatever
it
is,
you
know,
put
it
in
that,
put
it
in
that
yaml
file
or
in
that
deny
file,
and
you
know
we'll,
never
collect
it.
B
We
don't
want
anything
to
do
with
it,
but
it
is
important
to
note
if
you
say
I
don't
want
you
to
collect
anything
having
to
do
with
the
networking
staff.
Then
we
potentially
couldn't
tell
you
something
about
like
that.
That
early
example
of
a
of
a
bonding
issue-
maybe
we
wouldn't
know
because
we're
not
collecting
that
stuff,
but
overall,
like
I,
I
think
the
information
that's
collected
is
it's
fairly
innocuous.
It's
all
metadata
and
you
you
have
the
control
over.
B
A
Yeah
in
insights,
I
said
this
at
the
top
of
the
show,
but
it's
worth
repeating.
I
wish
I
had
this
as
a
sysadmin.
It
would
have
saved
so
many
hours
of
I
mean,
let's
face
it.
A
lot
of
these
fixes
are
update
this
package
or
disable
this
service,
unless
absolutely
necessary
things
that
are
literally
one
command,
but
you'd
have
her
repeat
that
command
400
times,
but
the
the
worst
part
of
it
was
the
the
research
that
went
ahead
of
it.
A
What
cvs
are
out
there
what's
affecting
me
and
then
manually
going
in
and
doing
that
research
I
mean
that
part
took
a
hundred
times
what
it
takes
to
just
fix
the
actual
issue
and
with
insights
it's
all
collected.
For
me,
it's
brought
up
in
the
background
I
mean
it's,
it's
an
amazing
tool
and
whether
you've
got
10
servers
or
100
servers
or
10
000
servers.
It's
I
mean
it's
this.
This
saves
so
much
time
and
we
only
dug
into
the
vulnerability
and
we
glanced
at
the
remediation
pieces.
A
B
A
I
love
how
much
insights
has
grown
and
how
much
it's
it's
tying
into
all
of
our
other
other
products,
whether
that's
rel
or
openshift,
or
even
some
of
the
add-on
products
like
like
satellite
or
I
forgot
what
what
other
ones
I
was
going
to
mention
or
ansible
was
was
the
other
one
and
just
how
much
all
the
stuff
interacts
now
it
makes
it
so
easy
to
be
a
systems
administrator,
especially
in
an
age
where
security
is
becoming
more
and
more
critical
and
the
the
infrastructure
is
becoming
more
complex.
It's
it's
not!
A
Everything
is
built
behind
castle
walls
and
emote.
Now
now
we've
got
multiple
castles
and
then
we've
got
we've
got
stuff
in
towns.
So
you
know,
of
course,
I'm
alluding
to
this
whole
hybrid
multi-cloud
change,
I
mean
zero
trust
is,
is
becoming
more
and
more
prevalent,
and
all
of
these
are
things
that
we
should.
We
should
definitely
talk
about
more
on
on
this
show
and
john
obviously,
you've
you've
written
up
about
about
another
16
or
so
episodes
that
we
could
do,
but.
B
Go
ahead!
One
last
thing:
I
want
to
reiterate,
as
we've
talked
through
this
again,
it's
included
with
your
existing
rail
subscription,
and
that
is
true.
If
you're
a
developer,
if
you're
in
you
know
full
out
on-premise
server
user,
if
you're,
using
aws
or
azure,
you
know
you're
using
rel
in
the
cloud
and
even
if
you're
buying
that
rel
in
the
cloud
from
the
marketplace,
divider
you're,
buying
that
rail
from
aws
you're
buying
it
from
azure.
You
still
get
insights,
it's
there
for
you
check.
A
It
out
yeah
by
all
means
play
with
it.
So
that's
that's
actually
a
perfect
jumping
off
point
to
mention
that
we
have
a
discord
server.
So,
if
you'll,
if
you
look
in
the
show
notes
of
this
episode,
you
can
get
a
link
out
to
our
discord
server.
I'm
there
a
few
of
the
other
hosts.
Are
there
it's
a
growing
community.
A
I
think
10
new
people
have
joined
in
the
last
like
three
days.
So,
if
you
haven't
joined
our
discord
server
by
all
means
jump
out.
There
ask
questions.
Folks,
like
myself,
and
some
of
the
other
hosts
can
reach
out
to
folks
like
john
to
to
answer
questions
to
kind
of
help.
Talk
talk
you
through
this
because
this
this
may
be.
This
may
be
a
live
stream
a
show,
but
the
the
reality
is
without
our
community.
A
Without
those
of
you
that
jump
on
every
couple
of
weeks
and
join
us
live,
you
know
we're
it's
just
john
and
I
sitting
here
having
a
conversation,
so
those
conversations
are
so
much
better
when
you
join
in
you
can
reach
me
on
twitter,
at
itguyeric
and
I'll
drag
john
kicking
and
screaming
onto
twitter.
A
little
bit
more
often,
but
you
can
reach
him
at
jbsphinx
and
we're
we're
more
than
happy
to
to
answer
those
questions.
A
B
A
B
A
3
pm
now
so
we
start
at
about
2
p.m:
central
or
2pm,
eastern
every
other
wednesday,
and
you
can
now
catch
us
on.
You
can
catch
the
live
chat
on
discord.
You
can
join
us
over
twitch,
open,
openshift
youtube,
and
as
of
this
episode,
you
can
catch
us
live
on
red
hat
enterprise.
Linux,
youtube
channel.
All
those
links
will
be
in
the
show
notes,
john
on
on
behalf
of
of
all
of
us
that
watch
today
and
we'll
watch
in
the
coming
days.
Thank
you
so
much
for
joining
us.