►
Description
Don't miss out! Join us at our upcoming event: KubeCon + CloudNativeCon Europe in Amsterdam, The Netherlands from 18 - 21 April, 2023. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.
A
A
How
can
we
be
certain
on
the
effectiveness
of
our
security
tooling
and
then
I'll
give
a
quick
demo
of
Paladin
Cloud
I'm
going
over
its
use
in
security,
efficacy,
so
a
holistic
approach
to
managing
cyber
assets
and
extending
your
security
posture?
That's
a
mouthful
so
I'm
going
to
break
that
down
into
three
parts.
We've
got
a
holistic
approach.
This
is
characterized
by
the
belief
that
the
parts
of
something
are
interconnected
and
can
be
explained
only
by
a
reference
to
the
whole.
What
does
this
mean
in
the
context
of
cyber
assets?
A
A
Similarly,
attackers
are
looking
at
more
than
compromising
one
asset,
but
rather
how
to
use
a
single
compromised
asset
to
move
laterally
into
other
parts
of
an
organization's
infrastructure.
Then
we
have
managing
cyber
assets.
What's
a
cyber
asset
according
to
nist,
it's
the
data,
Personnel
devices
systems
and
Facilities
that
enable
the
organization
to
achieve
business
purposes.
A
A
A
But
how
do
we
get
here?
Moving
to
the
cloud
brings
many
benefits
to
an
organization,
so
digital
transformation
or
moving
to
the
cloud
allows
organizations
greater
scalability
and
flexibility,
and
this
helps
organizations
respond
quickly
to
changing
business
needs.
The
specifics
vary
by
organization,
but
they
fall
into
three
big
buckets,
we'll
discuss
later
on
Operations
Security
and
cost.
However,
as
organizations
move
more
of
their
operations
to
the
cloud,
it
is
crucial
that
their
security
posture
is
maintain
and
that
cyber
assets
are
appropriately
managed
and
secured.
A
Let's
start
with
this
concept
of
digital
transformation,
digital
transformation
has
been
going
on
for
a
while
developers
needed
Computing
resources
for
their
applications
in
the
past.
That
was
all
built
locally,
so
we
had
all
this
on
premise
infrastructure
and
that
meant
requesting
an
operations
team
to
handle
requisitioning
and
provisioning
the
assets
needed
by
the
teams
developing
applications.
A
When
we
talk
about
efficiency
in
the
cloud,
a
lot
of
that
is
from
devops
the
abilities
for
developers
to
spin
up
environments
on
demand
quickly
as
cloud
computing
becomes
available,
the
efficiency
and
cost
saving
of
not
needing
a
whole
Ops
Team
becomes
more
and
more
attractive.
Organizations
begin
to
realize
that
the
value
of
digital
transformation,
but
now
needed
to
figure
out
how
they
were
going
to
accomplish
it.
There
are
three
main
ways
to
tackle
digital
transformation.
A
One
of
those
is
a
lift
and
shift
or
migration
here,
you're
moving
existing
applications
to
the
cloud
with
minimal
changes
use
this
strategy
when
the
goal
is
to
reduce
costs,
increase,
scalability
or
you're
under
a
time
crunch
re-architecture.
This
involves
reimagining
existing
applications
to
take
advantage
of
cloud
native
features,
use
this
strategy
when
the
goal
is
to
improve
performance,
scalability
and
flexibility,
and
then
there's
Cloud
native.
A
Some
organizations
hybrid
their
approach,
taking
different
strategies
for
different
applications,
but
choosing
which
one
is
correct
for
a
new
organization
should
be
based
on
their
goals.
For
why
they're
moving
to
cloud
in
the
first
place
at
a
previous
employer,
our
digital
transformation
from
on-premises
architecture
to
the
cloud
was
primarily
to
modernize
our
it
infrastructure,
increase
efficiency
and
reduce
costs.
We
ended
up
taking
the
lifted
shift
to
Route,
which
worked
to
reduce
our
costs
and
increase
scalability,
but
since
we
recreated
our
same
processes
in
the
cloud,
we
didn't
gain
very
much
in
performance
and
flexibility.
A
However,
since
we
renowned
the
cloud
we
have
those
options
open
to
us
in
the
future.
If
we
wanted
to
invest
in
them,
organizations
move
to
the
cloud
for
many
reasons,
but
they
usually
boil
down
to
one
of
these
time
to
value.
Speed
and
efficiency
are
big
motivators.
We
already
discussed
how
the
change
in
the
operations
model
can
provide
faster
time
to
value
by
removing
extra
steps.
A
Elasticity
scalability
is
an
enormous
benefit,
being
ready
for
and
available
for
crucial
moments
a
place
I
worked
at
previously.
We
hosted
some
of
the
presidential
debates.
Those
would
cause
huge
spikes
and
traffic,
so
we
need
to
be
able
to
scale
up
to
handle
that
load,
but
we
didn't
need
it
all
the
time.
So
the
cloud
scalability
ended
up
being
a
huge
draw
for
us.
A
A
Now
this
is
very
appealing,
but
remember
digital
transformation
isn't
a
magic
wand
done
poorly
teens
may
find
themselves
spending
even
more
money
and
finding
those
humans
were
providing
value
in
places.
Automation
can't
now
the
risk
of
going
backwards
from
doing
it.
Poorly
applies
to
all
of
these,
but
especially
this
next
one
security
by
offloading
security
to
the
cloud
provider.
Overall,
security
can
be
in
Pre
increased,
but
the
cloud
also
brings
its
swath
of
security
concerns.
A
Let's
look
at
what
that
security
responsibility.
Split
looks
like
this
is
an
example
from
AWS,
but
of
course,
gcp
Azure
and
other
Cloud
providers
have
very
similar
approaches
where
certain
security
aspects
are
offloaded
to
the
cloud
provider,
and
other
elements
are
still
owned
by
the
customer.
Aws
talks
about
this
in
terms
of
responsibility
for
security
of
the
cloud
and
responsibility
for
security
in
the
cloud
I
once
woke
up
from
a
sound
sleep
to
a
wrestling
sound
while
spending
the
night
alone
in
a
hotel
room,
I
was
freaked
out,
then
I
realized
the
source.
A
I
accidentally
left
the
door
to
a
shared
patio
open
and
a
breeze
was
wrestling
some
papers
I
left
out
the
night
before,
while
the
hotel
had
provided
security
of
my
room,
there
was
a
lock
on
the
door.
I
had
failed
to
handle
Security
in
my
room
by
leaving
that
door
wide
open.
Well,
thankfully,
nothing
happened,
but
it
was
a
vivid
reminder
of
my
role
in
my
own
security
being
on
the
cloud
opens
up
all
kinds
of
new
threat.
A
Vectors
AWS
gives
some
broad
examples
of
what
you
need
to
secure,
but
this
list
is
really
just
the
start,
that
fantastic
time
to
First
value
from
using
Dynamic
Cloud
environments
means
it's
also
really
easy
to
misconfigure
or
lose
track
of
things.
The
data
shows
that
enterprises
are
struggling
with
managing
security
and
compliance
inside
of
their
Cloud
Gartner
reported
that
nearly
all
successful
attacks
on
cloud
services
result
from
customers.
Customer
misconfiguration.
A
They
estimate,
as
the
Enterprises
could
avoid
80
percent
of
misconfigurations
by
adopting
security
posture
management
over
their
clouds.
Csos
and
security
teams
have
a
lot
to
deal
with,
but
here
are
some
of
the
top
concerns
that
we're
hearing
right
now,
trying
to
identify
threat
vectors
in
the
cloud
to
mitigate
risks
and
prevent
data
breaches,
ensuring
protection
over
their
sensitive
data,
focus
on
threat,
intelligence
and
risk
assessments
and
then
proactively,
monitoring
the
cloud
risks
with
automations
to
be
sure
that
they're
compliant.
A
So
how
do
organizations
get
a
handle
on
this?
The
first
step
is
for
them
to
understand
their
attack,
surface
understanding.
Your
attack,
Surface,
starts
with
a
thorough
and
complete
cyber
asset.
Inventory
and
inventory
has
been
a
fairly
common
practice
with
physical
assets,
but
the
cloud
changed
everything
think
about
the
definitions
we
discussed
at
the
start.
What
is
a
cyber
asset?
Remember
Ness
said
the
data
Personnel
devices
systems
and
Facilities
that
enable
the
organization
to
achieve
business
purposes.
A
It's
really
everything.
It's
configuration,
it's
your
databases,
your
apis,
your
clusters,
your
security
groups,
your
accounts,
everything
in
the
cloud
becomes
a
cyber
asset.
Your
attack
surface
has
changed
from
a
perimeter
like
a
castle
wall
with
a
moat
to
a
living
life
form.
Our
attack
service
is
now
like
a
coral
reef.
That's
constantly
changing
growing
and
shifting
it's
become
an
ecosystem.
A
In
the
past,
the
attack
surface
was
a
static
entity.
You
were
able
to
build
a
wall
around
it,
add
in
that
mode
and
keep
the
bad
folks
out.
As
long
as
nothing
got
past
your
perimeter,
you
were
confident
you
hadn't
been
breached
and
it's
most
rigorous.
The
idea
of
air
gap
security
worked
exceptionally
well,
but
now
the
Internet
connects
everything
we've
moved
to
this
Dynamic
world,
and
that
brings
all
kinds
of
unknown
risks.
We
no
longer
have
a
wall.
Our
moat
is
gone.
Our
perimeter
is
tens
of
thousands
of
entry
points
into
our
inner
Sanctum.
A
We
have
the
capabilities
for
developers
to
spin
up
entire
Stacks
at
once,
each
with
its
own
whole
level
of
complexity
and
security
concerns
we're
also
dealing
with
high-tech
threat
actors
and
nation-states
making
security
attacks
at
a
scale
that
we've
not
seen
before
our
attack
surface
is
no
longer
static.
It
is
a
living
entity
and
we
have
to
realize
we
will
never
go
back
and
that's
meant
a
move
to
defense
and
depth.
Implementing
network
security
via
stacks
of
controls.
A
All
kinds
of
security
tools
are
being
used
now,
as
this
proliferation
of
tools
comes
online
to
monitor
all
of
our
assets,
we
find
out
that
we
now
need
a
way
to
Monitor
and
consolidate
the
data
from
those
tools.
Otherwise,
teams
become
overwhelmed
by
so
many
tools
and
data
sources
coming
at
them
and
overwhelmed
teams
bulk
at
adoption.
They
were
resist
improvements
to
security.
A
A
We
recommend
create
a
group
dedicated
to
cyber
Asset
Management
time
and
again
we
see
that
successfully.
Managing
cyber
assets
involves
a
self-governing
group
forming
in
the
middle
of
an
organization.
The
group
goes
by
different
names,
the
cloud
Center
of
Excellence
devsecops,
Cloud
governance,
team,
or
something
else
that
aligns
with
their
organization's
culture,
but
the
name
isn't
what's
important,
it's
the
impact
they
bring.
This
group
focuses
on
the
three
key
things
to
governing
in
the
cloud
operations
cost
and
security.
A
A
How
do
you
make
sure
groups
aren't
throwing
money
away
in
my
personal
cloud,
I
forgot
to
do
cleanup
after
a
project
and
made
the
mistake
equivalent
of
leaving
the
water
running
while
I
was
on
vacation.
I
came
back
to
find
a
massive
bill
at
the
end
of
the
month.
Proper
Cloud
hygiene
and
optimizing
for
discounts
or
credits
can
save
organizations
large
amounts
of
money,
and
we
have
security,
of
course,
making
sure
to
minimize
risks
and
protect
against
threat.
A
Now
this
group
is
answering
the
question
of
what
does
a
healthy
Cloud
Model
look
like
to
answer.
What
healthy
looks
like
requires
that
they
understand
what
the
organization
wants
to
do
and
how
it
should
operate
within
the
cloud
at
any
organization
large
enough
to
need
a
cyber
Asset
Management
Group.
This
isn't
something
that's
done
in
a
day
or
even
a
week.
A
This
group
needs
to
consider
their
transition
strategy.
For
example,
their
goal
might
be
to
move
to
a
completely
Federated
workspace
in
the
cloud.
If
so,
that's
going
to
be
a
factor
in
the
policies
they
need
to
have.
This
group
must
tackle
the
challenge
that
important
security
concepts
are
often
far
more
aspirational
than
prescriptive.
A
A
It
doesn't
mean
these
Concepts
aren't
real,
but
we
as
a
community
of
practitioners,
aren't
yet
sure
what
the
best
way
to
do
all
these
things
is.
Similarly,
organizations
are
faced
with
defining
their
plans
to
get
to
zero
trust,
how
they
ensure
they
are
implementing
least
privileged
access.
Can
they
be
sure
users
only
have
access
to
what
they
need.
It
means
already.
Assuming
networks
have
been
compromised
because
we
no
longer
trust
the
idea
of
a
castle
wall
parameter.
Keeping
attackers
out.
A
Organizations
like
cncf
and
ossf
are
crucial
to
the
security
ecosystem
of
the
web.
They
help
shape
these
aspirational
goals,
Define
best
practices
and
give
direction
to
teams
looking
to
implement
these
practices
not
realize
this
is
really
hard
to
do.
The
Cyber
asset
management
team
needs
support
to
succeed
when
implementing
cyber
Asset
Management
teams
need
to
have
the
time
to
do
it
right.
They
need
to
have
support
from
leadership
to
implement
some
hard
choices
and
they
need
to
have
developer
buy-in
to
make
that
cultural
shift
happen.
A
They
need
to
be
sure
developers
are
included
in
security
conversations,
developers
tend
to
have
a
large
amount
of
operational
power
in
the
cloud
to
spin
up
the
assets
they
need
to
work.
Teams
can
often
go
to
the
cloud
provider
and
spin
up
an
entire
environment
or
even
provision
out
a
whole
kubernetes
cluster.
A
It's
not
unheard
of
for
teams
that
then
move
on
and
those
assets
get
left
behind,
creating
operational
cost
and
security
problems.
Therefore,
developers
engagement
is
critical
to
implementing
cyber
asset
management
and
extending
your
security
posture.
The
good
news
is,
most
developers
want
to
be
secure.
Sometimes
they
just
need
someone
to
give
them
now.
Security
is
also
complex.
Teams
often
need
to
be
informed
on
how
they
can
begin
tackling
such
a
daunting
task.
A
There
are
so
many
tools
and
platforms
out
there.
It
gets
overwhelming.
There
are
many
Cloud
providers
and
teams
are
often
running
multi-cloud.
We
have
vulnerability
scanners,
identity
management,
code
scanners,
kubernetes
management,
Asset,
Management
database
management,
data
compliance
and
a
large
number
of
SAS
tooling.
A
2020
blissfully
survey
found
that
a
medium
organization
averages
185
different
SAS
tools.
We
do
need
a
lot
of
tools,
but
throwing
teams
a
whole
bunch
of
different
tools
becomes
overwhelming.
A
A
So
how
do
we
get
to
the
right
information?
Well,
let's
go
back
to
our
definitions,
again
we're
looking
for
a
holistic
approach.
All
these
cyber
assets
are
interconnected
and
we
need
to
need
a
way
to
deal
with
them
individually
and
collectively,
and
by
deal
with
them
I
mean
we
need
to
extend
our
security
posture
over
them.
To
do
so,
we
need
a
policy
management
plane,
so
our
cyber
Asset
Management
policies
can
holistically
apply
to
all
of
our
cyber
assets.
A
We
start
by
defining
all
our
cyber
assets.
Then
we
take
the
Cyber
Asset
Management
policies,
our
Cloud
team
created
and
apply
those
across
all
our
assets.
Once
that's
in
place,
we
then
automate
the
monitoring
of
those
assets
against
our
security
posture,
so
we
can
know
the
state
of
our
cloud
in
real
time.
A
The
end
goal
is
to
observe
and
automate
everything
with
that
in
place.
We
can
now
look
at
our
cloud
and
understand
our
attack
surface.
In
addition,
we
can
visualize
how
it
is
changing
over
time
and
understand
the
trends
of
our
compliance.
That
brings
us
to
a
concept
called
security.
Efficacy,
efficacy
is
the
ability
to
produce
a
desired
or
intended
result.
Let
me
give
an
example
of
what
I
mean
by
efficacy.
A
I
worked
with
an
organization
that
adapted
qualis
to
do
scanning
of
their
compute
instances.
They
were
getting
good
results
back
from
their
scans.
They
thought
hey.
We
are
secure,
but
come
to
find
out
as
they
begin
identifying
all
of
their
cyber
assets.
There
were
a
bunch
of
instances
they
hadn't
been
aware
of,
and
those
were
not
being
scanned.
A
There
was
nothing
wrong
with
the
tool
they
chose,
but
the
actual
efficacy
of
that
tool
was
Far
lower
than
they
realized
because
they
didn't
know
their
attack
service.
This
idea
of
security
efficacy
is
about
getting
the
most
out
of
the
tools
available.
If
we
don't
have
a
cyber
asset
inventory,
then
we
don't
have
a
way
to
verify.
We
are
taking
a
holistic
approach.
We
then
think
we're
fully
protected
when
we
aren't
it's
important
to
know
is
our
efficacy
at
99,
90
or
50
percent.
A
A
The
other
aspect
of
efficacy
is
around
time.
How
long
are
vulnerable
assets
sitting
around?
Does
your
cyber
Asset
Management
cover?
How
long
teams
have
to
address
critical
issues?
Is
this
measured
in
terms
of
hours
or
in
weeks,
for
example,
if
it
takes
three
weeks
to
fix
a
publicly
exposed
asset?
Your
security
efficacy
is
much
lower
than
a
team
that
addresses
those
within
24
hours.
A
Having
scanning
and
monitoring
is
a
step
forward,
but
security
efficacy
is
about
understanding
the
effectiveness
of
those
tools
and
policies
tracking
the
efficacy
of
your
security
posture
lets
you
be
certain.
It
extends
over
your
entire
attack
surface,
let's
wrap
up
here
with
a
review.
First,
we
discussed
a
holistic
approach
to
managing
cyber
Assets
in
a
extending
your
security
posture.
We
broke
that
down
into
its
three
parts:
the
holistic
approach,
managing
the
Cyber
assets
and
extending
security
posture.
A
We
examine
how
and
why
organizations
adopt
digital
transformation
and
move
to
the
cloud
then
covered
how
security
is
a
responsibility
shared
with
the
cloud
providers.
Moving
to
the
cloud
forever
changed
our
attack
Services.
We
have
less
left
the
static
castles
of
the
past
and
when
must
now
secure
the
dynamic
morphing
ecosystems
of
modern
clouds
to
deal
with
this
new
shifting
reality,
organizations
must
understand
their
attack
Surface
by
identifying
their
cyber
assets,
creating
holistic,
cyber
Asset
Management
policies
and
then
extending
their
security
posture
by
automating
and
Reporting
on
the
efficacy
of
those
policies,
as
promised.
A
Here's
a
quick
demo
of
what
measuring
this
using
open
source
tooling
looks
like
Paladin
cloud
is
a
free,
open
source
security
as
code
platform.
That's
working
to
address
these
challenges.
Let's
take
a
look
at
how
it
enables
teams
to
manage
their
cyber
assets.
Paladin
Cloud
scans,
your
Cloud
infrastructure,
locating
assets
on
any
account.
You
give
it
for
this
demo,
we'll
use
data
from
our
three
Cloud
providers
pulling
in
assets
from
AWS,
Azure
and
gcp
Paladin
cloud
has
over
400
policies
built
in
and
allows
you
to
write
custom
policies
for
your
specific
organization.
A
Anytime,
an
asset
fails
to
follow
one
of
those
policies
that
creates
a
violation
we
can
see
here
in
our
demo
account
that
we
have
just
over
300
assets,
and
here
in
the
dashboard,
we
can
see
a
breakdown
of
all
of
our
violations.
First
off
they're,
sorted
by
criticality,
so
we
know
what
to
focus
on.
We
could
see
that
we
have
79
critical
violations.
These
are
the
ones
that
need
to
be
addressed
first
now
we
get
information
about
those.
So
we
can
see
that
even
though
there's
79
critical
violations,
those
are
across
just
20
policies.
A
So
we'll
want
to
look
at
those
policies
to
understand.
If
we
can
get
some
quick
wins
here
by
locating
which
ones
we're
have
the
most
violations
with
and
resolving
those.
We
can
see
that
that
runs
across
43
assets,
so
kind
of
in
general,
each
one
of
these
assets.
It
has
two
different
critical
violations
and
then,
after
that,
we
have
the
average
time
it
takes
for
our
team
to
remediate
these
violations
as
they
come
in,
and
so
we
can
see
here.
We
have
two
days
to
remediate
critical
violations.
A
A
Now
the
different
policies
that
we
have
are
broken
down
into
four
categories:
there's
the
security
which
makes
up
the
majority
of
our
policies,
but
we
also
have
policies
in
here
around
cost,
saving
money,
operational
policies
and
then
tagging
tagging
is
so
important
to
understanding
your
cyber
assets
that
it
gets
its
own
category
and
its
own
whole
section
in
the
UI
that
we'll
look
at
here
in
a
couple
minutes
below
that
we
could
see
asset
graph.
This
charts
are
total
assets
over
time.
This
can
be
really
helpful
for
understanding
what
your
usage
looks
like
do.
A
You
have
regular
Peaks
and
valleys.
It's
also
important
for
identifying
anomalies
and
understanding
what's
going
on.
If
you
have
a
large
drop
or
a
large
gain
in
assets,
it's
important
to
know
why
that's
happening
it
can
help
you
do
early
detection
of
a
possible
breach
or
at
least
understand
what
your
teams
are
doing
as
they're
removing
or
creating
new
assets
in
your
environment,
and
then
we
can
get
to
our
policy
compliance
overview.
This
lists
out
all
of
our
different
violations
by
policy
and
tells
us
how
many
we
have
of
each
one.
A
So
this
is
helpful
when
you're
trying
to
prioritize
what
to
prioritize
what
to
work
on.
We
could
see
that
our
the
policy
with
the
most
violations
here
is
a
signing
mandatory
tags.
We've
got
a
lot
of
work
to
do
on
tagging,
so
we
could
start
in
here
tagging
things
to
bring
this
down.
We
might
also
want
to
look
at
by
severity,
so
we
could
see.
Deny
Public.
Access
here
is
the
the
critical
policy
that
has
the
most
violations,
another
great
spot
for
our
teams
to
begin
working
at
now.
A
These
violations,
we
can
dig
into
those
we
saw.
We
have
400
different
violations.
These
violations
we
can.
We
can
filter
those.
This
is
a
large
list,
but
we
can
come
up
here
and
we
can
filter
those
as
needed
and
by
the
account
by
severity.
So
let's
say
we
want
to
look
just
at
all
of
our
our
critical
ones,
so
we
can
see
just
look
at
those.
Let's
look
for
ec2.
We
see
some
of
those,
so
we
can
pull
up
just
the
the
item
specific
for
that.
A
So
let's
dig
into
one
of
these
we'll
click
in
here,
and
so
we
can
from
that
list.
We
can
now
dig
into
the
specific
violation.
So
here
we
can
see
the
status
is
open.
Let's
say
this
needed
to
be
open
for
a
certain
amount
of
time.
We
might
request
an
exemption,
so
an
exemption
can
get
added
in
here
now
I'm
in
the
role
of
an
admin,
so
I
can
add
them.
If
you're
a
user,
you
can
only
request
it
and
have
to
have
an
admin
approve
that
we
can
see.
This
is
critical.
A
A
So
by
doing
this,
that
brings
us
to
our
assets
and
now
we're
looking
at
the
details
for
this
specific
ec2
instance.
We
get
an
idea
of
its
overall
compliance,
so
we
can
see
we're
actually
doing
pretty
well
on
here,
except
for
this
one
very
important,
critical
item
that
needs
to
be
addressed.
Information
over
here
on
on
where
this
exists.
We
could
use
that
information
to
go
in
locate
this
and
and
resolve
this
issue.
A
While
we're
looking
at
specific
assets,
we
can
look
at
our
distribution,
so
this
gives
us
a
heat
map
of
all
of
our
different
assets
that
we
have,
and
this
can
be
really
helpful,
to
understand
the
proportion
and
how
you're,
using
all
of
your
different
Assets
in
the
cloud
we've
had.
People
come
in
install
this
and,
and
one
group
found
that
they
had
tens
of
thousands
of
Amis
that
they
didn't
know
about.
A
As
they
began
cleaning
up
those
and
cleaning
up
their
snapshots,
they
ended
up
saving
over
a
million
dollars
by
better
understanding
what
their
Cloud
looked
like.
They
didn't
know
that
all
these
assets
were
sitting
out
there,
so
understanding
the
layout
of
your
your
attack
surface
understanding.
What
that
looks
like
can
be
important
to
saving
money
but
also
being
more
secure,
and
then
we
have
the
tagging
section
here.
A
Even
if
you've
got
all
these
different
cyber
assets
added
in
here,
knowing
what
they
do
is
important
and
if
they
aren't
tagged
well,
you
can
just
have
them
sitting
there
and
not
knowing
the
purpose
or
how
to
handle
those.
So
we
really
want
tagging
to
be
a
first-class
citizen
here
we
could
see
that
in
this
we
could
check
our
total
tag
and
compliance.
A
We
can
even
see
our
mandatory
tags
for
our
organization
over
here
and
how
we're
following
those
and
we
can
even
look
at
different,
specific
asset
types
and
dig
into
those
which
ones
are
tagged
and
not
and
work
to
remediate
those
now.
Hopefully,
this
has
been
helpful
for
you
to
understand
how
a
team
can
come
in
here
and
better
understand
their
total
cyber
assets
be
able
to
manage
those
and
how
the
automation
can
allow
them
to
extend
their
security
posture
over
that
whole
attack
surface.