►
From YouTube: Tool House Rock #9 | Hypernative
Description
MakerDAO Forum Post: https://forum.makerdao.com/t/tool-house-rock-9-hypernative-tuesday-june-13-2023-14-00-utc/21023
Description
Tool House Rock is a structured community call to give projects a way to showcase their tools and solutions to the growing MakerDAO Ecosystem. Tool House Rock will follow a consistent call agenda, focused on giving Ecosystem Actors a foundation for reviewing and assessing tools.
This Session's Guest: Gal Sagie - https://twitter.com/GalSagie
What is Hypernative?
Hypernative is a tool that utilizes machine learning, correlations, heuristics, and anomalies to create more than 200+ detectors that trigger alerts that can drive internal playbooks and processes. Hypernative stops zero-day Web3 cyber-attacks, economic risks and protects digital assets, protocols and Web3 applications from significant losses by preemptively detecting risks and integrating response workflows using APIs, email, and other platforms.
Hypernative is designed for:
* Detecting real-time hacks and market risks before significant loss
* Using both on-chain and off-chain data for risk analysis
* Building and enabling preventative workflows
Disclaimer
This communication is provided for information purposes only. The views and opinions expressed in this meeting are those of people involved and do not reflect the official policy or position of MakerDAO or any of its contributors, Core Units, or affiliates. This communication makes no representations about the enduring accuracy of the information or its appropriateness for a given situation. This content is provided for informational purposes only and should not be relied upon as legal, business, investment, financial, or tax advice. You should consult your own advisers as to those matters. References to any digital assets and the use of finance-related terminology are for illustrative purposes only and do not constitute any recommendation for any action or an offer to provide investment, financial, or other advisory services.
MakerDAO Links:
https://makerendgame.com
https://mips.makerdao.com
https://forum.makerdao.com
https://chat.makerdao.com
A
A
B
So
I'll
present
in
this
mode,
because
otherwise
it
doesn't
work
so
hi,
hi,
everyone,
I'm
I'm,
gal,
CEO
and
co-founder
of
hyper
native
a
little
bit
about
background
about
myself
and
Hyper
native,
so
I'm,
coming
from
traditional
cyber
security
and
Cloud
infrastructure.
Space
I
sold
my
last
company
to
IBM
a
few
years
ago
and
then
was
CTO
and
IBM
cloud
and
various
roles
at
Google,
VMware,
Huawei
and
the
government.
Here
in
Israel
myself
and
my
co-founder
started
hypernative,
because
we
saw
the
huge
amounts
of
money
that
are
being
stolen
from
protocols.
B
We
saw
people
getting
fished
and
scam
and
we
fought
in
in
high
level
understanding
and
mitigating
risk
and
security,
detecting
the
risk
and
then
preventing.
It
is
something
that
needs
Improvement
in
space,
and
this
is
why
we
created
hypernative
I'm,
going
to
go
through
what
what
we're
doing
at
hyper
native
and
what
the
system
is
looking,
looks
like
and
then
do
a
demo
of
the
system.
And
please
anyone
stop
me
if
you
have
any
questions.
B
So
the
main
problem
that
that
we
saw
when
we
started
hypernative
is
that
it
really
focused
on
audits,
like
protocols
and
chains.
All
we've
done
audit
from
one
sometimes
even
more
vendors
and
as
Oddities
is
a
great
great
first
thing.
But
when
you
look
at
security,
it's
usually
alert
approach
where
you
want
to
have
various
layers
of
protection
when
you
really
want
to
mitigate
and
prevent
risk.
B
So
there
are
a
few.
There
are
a
few
issues,
main
issues
with
audits
today,
so
I
think
the
major
one
is
that
an
audit
is,
in
the
end,
a
manual
process
right.
It's
it's
people,
looking
looking
at
your
code
and
trying
to
find
all
sorts
of
things,
this
makes
this
process
relatively
slow
and
expensive
and
it
really
limits
the
scale
right
of
the
Innovation,
because
now,
if
you
really
want
to
make
it
right,
you
need
to
audit
every
change
and
every
new
project
that
is
being
created.
B
Then
the
bottleneck
becomes
the
people
and
the
expertise
of
the
people
that
are
actually
reviewing
the
code,
and
this
leads
to
the
the
next
problem,
which
is
something
that
we
call
an
audit
drift.
Basically,
what
happens
is
that
you,
you
do
an
audit,
sometimes
even
few
audits,
but
then
you
start
making
these
small
changes
that
you
think.
Okay,
yeah:
this
change
is
probably
not
going
to
harm
me
or
this
change
is
is
relatively
small.
So
why
should
I
wait
a
few
weeks
or
a
few
months
to
get
an
audit?
B
And
this
is
where
vulnerabilities
and
Tech
surfaces
are
actually
enters
and
I
think
the
main,
the
main
part
is
also
that
an
audit
doesn't
in
the
end
it
doesn't
cover
all
the
various
attack
vectors
and
it
misses
a
lot
of
the
flows
that
are.
Are
there
because
again
people
make
mistakes?
There
isn't
a
perfect
audit
and
it's
really
hard
to
think
about
all
the
various
conditions
and
market
conditions
and
integration
with
third
parties
and
various
things
that
that
could
happen
to
to
your
project.
B
So
we
we
realized
that
real-time
monitoring
is
important
and
the
common
monitoring
is
just
not
enough.
We
need
a
real-time
market
and
systemic
risk
detection
system.
That
knows
to
essentially
discover
risk
and
discover
them
in
a
in
a
way
that
is
actionable
like
if
you,
if
you
find
a
security
problem
or
if
you
find
a
risk-
and
you
can't
do
anything
about
it-
it's
like
you,
you
haven't
found
it
at
all
right.
B
So
you
need
to
find
these
things
before
they
happen
in
a
in
an
actionable
manner
and
you
and
it's
not
enough
to
just
monitor
like
in
variants
or
specific
things
in
the
in
the
protocol.
You
need
to
really
look
at
monitoring
and
detection
of
risk
in
a
very
holistic
manner,
and
this
is
exactly
what
typer
native
is
doing.
B
We
were
involved
and
a
lot
of
times
because
even
for
non-customers,
we
still
try
to
warn
them
like
if
we
see
a
protocol
that
is
getting
hacked
and
the
way
that
we
see
it
is
today.
Hypernative
looks
at
the
entire
chain.
Like
we
look
at
all
the
contracts.
We
look
at
all
the
governance
proposal.
We
look
at
all
the
transactions.
We
look
at
all
the
contracts
that
are
being
created
on
chain
and
that
help
us
really
Map
and
find
things
even
for
non-customers
of
hypernative,
like
we
were
detect
in
the
Euler
hack.
B
B
Like
the
oracles
that
you
integrate
with
the
bridges
other
protocols
that
might
relate
or
can
damage
you,
because,
for
example,
you
are
trading
your
token
in
the
same
pool
as
them
and
so
on,
so
monitoring
of
risk
must
be
holistic,
end-to-end
capability
and
the
general
way
that
hypernative
works
and-
and
this
is
an
example
of
how
we
work,
there
are
various
other
kind
of
methods,
but
the
first
thing
is
on
the
detection
right.
We,
the
system
knows
to
detect
risk
and
risk
can
be
very
specific.
B
B
And
this
is
something
that,
if
you're
interested
I
would
love
to
discuss
more
on
Discover
on
a
private
discussion.
So
when
we
we
hope
to
expose
more
of
that
in
the
coming
months.
About
that,
we
are
feeling
very
excited,
because
we
really
believe
that
what
we
are
building
here
can
mitigate
a
lot
of
the
big
bad
things
that
are
happening
today
in
crypto
and
web
3.
When
it
comes
to
security
and
on-chain
risk.
B
This
can
be
a
very
damaging
aspect
right,
even
if
there
isn't
any
hack
and
exploit
if
your
system
is
Crying,
Wolf
every
few
minutes
or
even
every
few
days,
and
this
detections
actually
actually
trigger
mitigation
actions.
That's
that's
a
very
bad
thing
and
I
think
that
hyper
native
today,
the
way
that
we
classify
detections,
we
don't
rely
on
basic
or
what
we
call
like
very,
very
common
ways
of
of
detecting
things.
B
For
example,
hyper
native
today,
we
are
not
looking
at
source
of
funds,
which
is
something
that
a
lot
of
Solutions
in
the
market
today,
look
at
which
we
found
out
is
very
problematic,
because
first
few,
various
attacks
are
happening
from
sources
that
are
not
necessarily,
for
example,
funded
by
tornado
cash,
and
we
saw
that
if
you
look
just
a
source
of
funds
as
a
way
to
detect
malicious
activity.
This
is
something
that
increase
the
the
false
positive
of
your
solution.
B
B
So
we
cover
a
big
set
of
risks
and
by
the
way,
a
lot
of
these
risks
could
be
also
customized
and
changed
by
the
user.
So
the
specific
project
teams
or
the
community
can
actually
configure
these
various
different
risk
types
and
set
different
thresholds
and
different
things
that
that
you
want
to
monitor
and
the
fourth.
The
fourth
bullet
is
completeness.
C
B
So
I
think
this
is
this
is
an
extensive
research
that
that
we've
done
we've
done
that
in
ethereum
since
Genesis.
Basically,
the
data
that
you
see
here
is
just
from
the
the
recent
month,
but
we
have
a
similar
research
that
we've
done
on
all
the
hex
and
exploit
that
happen
on
ethereum
since
Genesis.
By
the
way
we
ran
our
system
on
all
the
various
transaction
on
ethereum
from
Genesis.
B
Essentially,
we
saw
when
hyper
native
first
detected
the
hack
and
exploit
in
again
in
a
highly
accurate
manner
versus
the
time
that
the
first
hack
transaction
actually
happened
and
I
think
that
what
we
found
out
was
very
interesting.
What
we
found
out
that
in
more
than
97,
actually
that's
98
of
the
hex
and
exploit
in
the
various
in
the
last
few
years,
hyper
native
could
actually
detect
that
it's
two
minutes
and
more
before
for
the
first
tech
transaction.
B
So
two
minutes
and
more
and
if
you
consider
various
cases
even
days
before
the
first
tech,
transaction
and
I,
think
this
is
a
very
optimistic
result
which
shows
us
that
most
of
these
hacks
and
exploit
could
have
been
prevented
if
the
right
measures
were
present
to
handle.
Of
course,
this
detection
right-
and
this
really
depends
on
the
protocol,
but
I-
think
the
first
step
is
being
able
to
detect
the
hack
before
it
happened.
And
then
two
minutes
is
usually
more
than
enough
to
do
an
automated
process.
B
And
and
again
I
I,
you
know
when
we
started
like
when
we
started
a
year
ago.
This
was
really
not
clear
to
us.
This
was
really
not
clear
to
us,
and
this
was
from
all
the
discussions
that
we
had
people
kept
telling
us
that
this
is
not.
This
is
not
possible
and
I
think
that
you
know
once
we
got
into
this
stage,
that
we
can
do
this
testing
and
that
we
see
the
results.
I
I
think
that
we
have
proven
that
that
it
is
possible.
B
Think
the
critical
part
is
how
you
create
these
playbooks
of
what
is
risk
exactly
and
how
you
detect
the
risk
and
then
what
are
the
actions
that
are
needed
to
be
done
in
order
to
prevent
and
mitigate
the
risk?
Cannot
just
look
at
data
points
that
don't
really
say
a
lot
of
things
to
to
most
people
and
Hyper
native
today,
cover
is
from
compliance.
We
cover
risks
from
the
entire
governance
process,
which
is
especially
untrained
governance,
which
is
a
very
big
attack.
A
B
In
the
end,
governance
is
a
way
for
malicious
actors
to
insert
malicious,
either
code
or
anything
else
inside
the
project.
So
this
is
a
process
that
needs
to
be
monitored
and
detected
for
all
of
these
kind
of
different
risks.
We
see
Bridges,
which
are
a
big
attack
Vector
as
well.
Today
and
again,
Bridges
is
mandatory
that
your
solution
is
actually
monitoring
across
multi-chains
and
not
just
looking
at
one
chain
and
being
able
to
correlate
data
and
index
data
across
various
chains.
B
We
see
a
lot
of
economic
risk,
Market
risk,
Oracle
risk,
technical
wallets,
token
and
stable
coins
and
Community
around
phishing
scamming
and
fraud.
Detections
that
are
happening
quite
often
on
chain
and
Hyper
native
today,
as
a
system
is
able
to
really
detect
many
of
these
risks
and
provide
preventive
mechanism
for
most
of
them.
B
C
B
B
For
you,
where
we
see
the
integration
is
usually
on
the
preventive
side,
because
preventive
is
something
that
is
really
dependent
on
the
protocol
and
what
are
the
capabilities
of
the
protocol
and
even
from
a
philosophical
from
you
know,
what
is
the
protocol
willing
to
do
and
who
they
want
to
give
access
to,
and
this
is
something
that
is
semi
like
seamless,
because
some
of
it
we
support
in
the
platform.
But
then
some
work
needs
to
to
happen
from
the
protocol.
C
Nice,
but
let's
say
nowadays
like
if
we
find
today
like
a
potential
bug.
What's
what's
your
process
today,
do
you
guys
kind
of
like
look
for
a
back
Bounty,
or
do
you
just
tell
the
protocol
and
and
if
the
protocol
doesn't
pay,
you
you're
fine
with
it
like?
What's
what's
the
approach
you're
taking
there.
B
Yeah,
so
so
I
think
I
think
the
main
the
main
point
of
hype
for
Native
is
detecting
real-time
risks,
it's
less
about
finding
bugs
it's
more.
We
we
have
like
the
system
just
by
monitoring,
Behavior,
managed
to
really
detect
some
critical
vulnerability
bugs
for
some
of
our
customers,
but
the
idea
of
hypernative
is
to
really
detect
this
real
time.
B
Foreign.
You
know
risks
as
they
happen
and
then
alert
them.
So
our
customers
get
like
access
to
the
system
and
then
they
can
they
can
consume
all
the
alerts.
I'll
show
you
in
the
demo
how
it
looks
like
and
then
usually
we
work
with
them
to
Define
these
playbooks
of
okay,
what
to
do
with
various
detections.
So
they
are
getting
this
detection
they're
getting
these
detections
in
real
time
and
then
some
of
them
they
can
react
in
an
automated
Manner
and
some
of
them.
B
B
But
again
it's
not
an
optimal
process.
A
good
process
would
be
that
we
are
doing
a
process
to
Define
all
the
various
risks
that
that
could
apply
to
the
protocol.
We
are
building
these
detections
and
playbooks.
We
we
are
connecting
every
detection
or
every
Alert
in
the
system
to
the
process
that
we
need
to
do
and
basically
building
that
together
with
with
the
project.
C
Yeah,
it
makes
sense.
I
was
just
thinking
like
how
how
do
you
guys
avoid
the
kind
of
like
freeloader,
because
you,
you
kind
of
almost
feel
the
responsibility
to
sell
a
project
if
you
detect
something,
but
then
at
the
same
time,
you're
you're
doing
this
almost
for
for
free,
like
the
detection
part,
so
I
guess,
yeah
I
was
I,
was
thinking
about
the
freeloader
problem,
but
but
yeah
I
I.
B
Think
for
us
right,
like
our
main
in
the
end,
our
main
goal
is
to
make
the
ecosystem
safer,
I
think
from
looking
from
a
security
point
of
view
and
risk
point
of
view,
it's
it's
really
a
process
like
warning
someone
without
planning
before
like.
If
we
are
not
doing
this
planning
process,
it's
not
optimal,
we
are
usually
late
to
to
notify
you.
We
are
usually
helping
you
post
incident
after
you
got
hacked
so
in
order
to
really
mitigate
the
risk.
C
A
B
Yeah
sure
so
so
I
I
think
this
was
the
the
I
think
this
is
a
the
huge
differentiation
of
hyper
native
today.
Hypernative
does
the
classification
so
I
think
a
lot
of
like
the
approach
that
we
took
to
five
hex
and
exploit
is
instead
of
looking
at
specific
vulnerabilities
instead
of
monitoring
specific
vulnerabilities,
we
are
actually
monitoring
the
attacker
or
attack
symptoms
that
are
happening
basically,
preparation
to
the
attack.
B
We
see
that
the
false
positive
ratio
is
close
to
zero
at
this
point,
and
it's
improving
over
time,
so
I
believe
it
will
reach
something
very
close
to
to
zero
and
I.
Think
that
what
we
do
today
with
our
customers
is,
we
actually
tune
it
very
specifically
for
you.
So,
for
example,
if
you,
if
you
monitor
two
different
protocols,
their
monitoring
might
be
a
bit
different
right,
like
the
thresholds,
the
way
that
you
classify
things
as
malicious
or
not
could
be
different.
B
A
A
B
B
Anything
that
has
an
on-chain
address
that
you
want
to
monitor,
and
in
this
process
we
very
quickly
realize
that
people
don't
know
what
they
want
to
monitor,
because
again,
damage
can
come
in
crypto
from
all
sorts
of
you
know,
areas
and
things
that
are
not
necessarily
where
you're
looking.
So
this
is
the
first
IP
of
the
system.
B
B
Team
would
have
added,
as
you
saw
here,
there
are
some
of
the
protocol
contracts
essentially
or
the
multi-sig
wallets,
or
by
the
way,
the
governance
and
everything
that
they
want
to
monitor.
And,
as
you
see
here,
we
have
five
different
categories
of
of
risk
for
each
one.
We
have
a
lot
of
different
risk
insights
that
are
come
out
of
the
box.
B
We
also
have
something
called
custom
agents
that
are
basically
a
programmable
costume
Bots
that
you
can
Define
in
an
easy
manner
to
track
various
things
that
happened
on
chain
and
get
alerted
on
them,
and
these
chains
are.
These.
Things
are
basically
checked
every
every
block
or
every
time
interval
that
that
you
define
I'll
not
get
into
all
of
these.
But
please.
B
If
anyone
wants
to
see,
please
please
contact
us
later
and
we'll
be
happy
to
show
I
just
want
to
show
this
example
where
the
Jimbo
protocol
would
have
gotten
these
alerts
and
and
by
the
way,
the
alerts
that
you
see
here
is
are
again.
If
you
look
at
the
entire
history
of
this
protocol,
so
you
wouldn't
see
any
High
exploit
suspected
alert.
B
So
the
only
the
only
in
incident
where
the
system
actually
alerted
on
that
was
when
there
was
actually
a
hack,
and
this
hack
happened
on
the,
as
you
see
the
28
to
to
my
own
12
a.m:
24
UTC.
This
is
the
actual
hack
detection
and,
as
you
can
see,
hypernative
understand
who
is
the
attacker?
Who
is
the
wallet?
Who
is
the
contract
and
who
is
the
suspected
victim?
In
this
case?
Some
Contracting
Jimbo
protocol.
B
B
Thing
to
notice
is
that
the
system
actually
eight
minutes
before,
and
this
is
by
the
way
this
this
is
the
first
hack
transaction.
This
is
like
the
first
tech
transaction.
As
you
can
see,
there
were
various
other
hex
transactions
after
it,
but
I
think
that
the
interesting
part
to
see
here
is
that
the
system
actually
eight
minutes
before
or
six
seven
minutes
before
the
actual
hack
actually
alerted
on
an
exploit
suspected
which,
based
on
the
simulation,
so
the
system
actually
saw
that
Decker
getting
preparation
for
the
attack.
B
It
was
able
to
simulate
and
understand
the
outcome
of
that
attack
and
alerted
now
in
a
customer
setup.
That
alert
would
have
been
triggering
some
sort
of
a
mechanism
to
stop
this
attack
from
happening
either
from
pausing
the
contracts
or
blacklisting
the
specific
address
or
alert
acting.
You
know
the
relevant
people
by
even
a
phone
call,
if
needed
so
doing
doing
something
based
on
what
the
protocol
can
do
in
order
to
really
mitigate
the
risk.
C
Nice
regarding
I
mean
you
mentioned
the
you
mentioned
governance
girl.
How
do
you
make
a
difference
between
like
a
like?
What's
good
governance
or
I,
don't
know
I
guess
it
depends
who
you
are
right,
like
you're
you're,
your
Revolution
is
my
Insurrection
and
and
the
opposite.
So
how
do
you
make
sure
that
that
you're
dealing
with
the
right
issue
and
not
the
opposite.
B
A
A
B
So
audios
audios
is
is
a
is
a
web
Tree
Music
platform,
it's
on
I,
think
Solana
today,
but
it's
it
on
July.
Last
year
it
was
on
on
ethereum
and
it
got
hacked
it
got
by
the
way
audited
by
open,
Zeppelin
and
kudansky,
and
so
you
can
blame
them
for
picking
bad
Auditors
and
then
few
months
later
got
tagged.
It
actually
got
hacked
through
a
governance
proposal
which
which
happened.
B
There
was
some
bug
in
the
initialization
code,
but
I
think
this
case
and
by
the
way,
what
happened
for
Beanstalk.
If
you
heard
about
that
Tech
that
happened
on
April
last
year,
I
think
governance
are
in
the
in
the
end,
are
a
back
door
right
to
the
project
and
when
there
is
a
governance
proposal
there
is
the
description
right.
That
has
been
this
described
in
the
in
the
proposal.
B
What
hypernative
today
is
doing
is
actually
monitoring
every
on-chain
governance
proposal
for
all
sorts
of
various
things.
The
same
thing
that
we
are
doing
today
we
are
doing.
We
are
running
our
machine
learning
based
models
on
the
code
itself
in
order
to
find
you
know
maliciousness
in
the
code,
and
it's
not
just
these
models.
B
So
these
are
something
this
is
another
area
that
we
work
with
projects
and
protocols
today,
and
this
process
can
be
fully
integrated
right
into
the
governance
proposal
process.
So
every
governance
proposal
that
is
being
proposed,
hyper
native,
can
basically
create,
like
the
risk
score
for
this
proposal
and
provide
all
the
various
alerts
to
the
proposal.
We
are
doing
this
today
with
various
projects.
B
This
is
an
example
of
the
audience
which
happen
through
a
governance
proposal.
Like
six
million
worth
of
audience,
tokens
was
stolen,
so
six
million
dollars
was
stolen.
This
is
this
is
an
alert
that
actually
indicates
the
hack
itself.
As
you
can
see
here,
it
happened
on
1110,
PM
UTC,
and
this
hack
basically
say
that
there
this
is
a
proposal.
B
It
transfer
six
18.6
million
of
audio
tokens,
which
are
6
million
again
hypernative
calculate
all
of
these
prices
in
real
time,
based
on
on
and
off
chain
sources
which
are
99
of
the
tokens
in
the
protocol
treasury.
This
is
by
the
way,
suspicious
by
itself,
but
this
is
not
enough
for
us
to
actually
indicate
the
high
alert,
because
sometimes
that's
a
common
Behavior
right
for
some
Dows
or
for
some
treasuries.
B
So
there
are
a
lot
of
other
metadata
information
that
actually
made
hypernative
detect
that
this
is
high
risk,
and
this
is
the
actual
hacker
that
takes
all
of
these
tokens
out
of
the
treasury.
I
think
the
interesting
thing
to
see
here
is
that
actually
like
17
minutes
before
before
the
attack
hyper
native
on
10,
54,
PM,
UTC,
hyper
native,
actually
did
this
alert
right.
So
we
were
able
to
understand
that
this
is
a
suspicious
proposal
and
could
have
mitigated
it.
B
B
C
B
Yeah
and
and
I
think
to
me
every
on-chain
governance
by
the
way,
also
off-chain
governance,
but
I-
think
it's
critical
for
on-chain
governance
to
have
this
processes
that
are
done
in
real
time.
So
right
like
the
people
that
are
approving
their
requests
right,
they
they
don't
have
sometimes
the
capabilities
or
the
going
into
the
smaller
details
and
looking
at
all
the
various
different
bad
things
that
can
happen
in
a
proposal,
so
I
think
right,
it's
and
sometimes
by
the
way
by
mistake
right.
B
Sometimes
it
could
be
a
mistake
that
that
is
done
and
it's
actually
exposing
the
protocol
to
something
bad
that
can
be
detected
through
a
simulation
of
that
proposal
and
testing
of
various
different
fuzzing
techniques
and
things
that
that
we
currently
do
with
in
hypernative.
So
I
think
this
is
to
me.
This
is
a
mandatory
process
that
every
online
governance
needs
to
go
for
every
proposal.
B
Sure
so
we
have
today
tiers
of
monthly
subscription
which
are
based
on
the
feature
that
you're
leveraging
from
from
the
platform.
If
there
is
any
specific
customization
that
is
done,
for
example,
for
the
preventive
measures
and
on
the
higher
ends
of
the
of
the
tiers.
It's
sometimes
what
hyper
native
do
a
lot
of
protocols
and
projects,
don't
really
have
a
security
person
or
a
security
team
in-house.
B
What
we
do
today
is
not
just
give
you
this
platform,
and
let
you
you
know,
configure
it
and
use
it
by
yourself,
but
we
see
ourselves
as
an
extension
or
of
an
augmentation
of
your
or
a
creation,
sometimes
because
you
don't
even
have
one
person
of
that
security
team,
and
we
basically
help
you
also
manage
the
tool
detect.
These
things
investigate
all
the
various
you
know,
alerts
that
might
be
triggered,
and
this
is
something
that
we
do
with
with
the
higher
end
customers
today.