►
From YouTube: Pipeline Security Team Meeting AMER 2023-03-30
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
There's
like
a
lot
of
vacations,
just
to
be
aware
of
that
lots
of
folks
taking
time
off
in
the
next
few
weeks.
I'm.
Also
oh
I,
didn't
add
myself
I'm
also
going
to
take
off
parts
of
spring
break
so.
A
Returning,
let's
see
I,
think
the
fourth
he
said,
maybe
so,
just
just
a
heads
up
if
you're
not
getting
responses
from
someone
lately,
it
seems
like
this
is
a
vacation
season,
so
yeah
just
a
heads
up
and
then
also
as
you're
working
along
just
a
reminder.
A
Please
update
your
workflow
status
because
that
means
you
don't
have
to
hear
from
me,
which
you
know
some
people
like
so
yeah,
that's
my
big
things
and
then
I
don't
know
did
either
of
you
get
the
chance
to
watch
the
video
on
the
incident
yeah.
The
meeting
not.
A
Didn't
watch
the
video
yet
either,
but
it
seems
like
when,
okay,
when
there
was
an
attempt
to
actually
unlock
all
the
things
that
were
like.
Oh
those
shouldn't,
be
locked.
A
C
It
sounds
like
even
the
database
review
process
didn't
catch
it
as
it
may.
Maybe
it
should
have
so
lots
of
things
to
think
about
I
guess,
yeah.
A
A
I
think
it's
us,
because
this
was
from
our
end,
but
I
think
there's
other
people
who
are
definitely
looking
at
it
like
I
know,
Meg
his
his
verbalize
on
a
couple
of
like
slack,
drives
and
stuff
right,
like
so
I
I
think
like
we
are
taking
like
that
first
step
of
identifying
like
root
cause
and
stuff,
but
it's
definitely
gonna
be
greater
than
this
team.
A
When
we
do
I'm
trying
to
remember
the
there's
like
I,
think,
there's
like
a
corrective
action
or
like
a
Coe
I
think
that's
gonna
follow
this
so
I
think,
like
a
lot
of
other
people
will
be
involved
too,
especially
if
we're
having
a
question
of
like
hey.
Should
the
database
team
have
identified
this
in
advance
right
so
yeah
you
know
like
we
are
hopefully
not
trying
to
fix
something
and
avoid.
A
The
gift
that
never
stops
giving
I
believe
that's
how
I
constantly
describe
it
so
so
yeah
I
think
I
was
a
little
confused
as
to
like
what
what
things
should
be
stalled,
but
I
do
think.
The
front
end
should
be
fine.
I
know
Eric,
who
is
trying
to
figure
out
whether
or
not
skip
copy
work
was
was
on
pause
or
not.
A
A
Cool
and
then
the
other
thing
that
we
have
here
is
the
Azure
integration.
Someone
on
the
juhu
team
has
been
working
on
that,
and
so
we
just
need
to
I
think
go
through
make
sure
that
everything
is
being
contributed.
Actually
I
does
what
it
needs
to,
and
so
I
know.
A
This
is
one
that,
like
our
team,
hasn't
been
super
involved
in,
but
just
a
heads
up
that
that
is
in
work,
and
we
also
will
need
to
think
about
to
how
we
can
maybe
adapt
some
of
the
things
that
were
done
with
the
Vault
integration.
A
This
Azure
integration,
when
we
move
forward
to
the
AWS
integration,
so
some
good
documentation
there
that
Albert
has
linked
or
Max
or
Albert
linked
or
for
that
integration,
because
we
are
going
to
still
Focus
I
think
fairly
heavily
on
the
third
party
Integrations
for
a
while.
A
Cool
and
then,
let's
see,
Albert
had
his
discussion
on
secrets
of
IDC
and
the
ID
token
and
posted
his
recording
yeah.
Did
you
want
to
voice
over.
B
Sure
I
just
thought,
like
I'm,
adding
my
points
to
the
big
read-only
section
but
turns
out
the
whole
agenda
is
read
only
today
anyway,
yeah
so
I
was
trying
to
find
a
yaml
file
that
I
can
use
to
test
like
when
there's
a
manual
job.
That
requires
a
variable
input
to
proceed
to
run
a
form
appears
on
the
on
the
job
logs
page
and
somehow
I
was
just
not
able
to
find
it.
Then
I
resorted
to
slack.
B
We
had
a
discussion
on
the
verified,
Channel
and
then
Lee
also
helped
and
I
have
created
a
sample
project
in
the
CI
samples
so
that
it
doesn't
get
lost
again
and
we
have
something
always,
and
the
next
point
is
Jocelyn
and
I.
We
used
our
previous
one-on-one
to
work
on
a
vision
statement
for
our
group,
which
is
like
here
to
be
updated
to
the
handbook.
B
So
this
is
our
new
vision.
We
enable
organizations
to
adopt
good
practices
for
secure
handling
of
their
sensitive
information
and
data
and
below
that
is
a
Ural
link
like
the
mural
sort
of
template
that
we
use
to
have
the
discussion
yeah.
Nothing
as
interesting
as
the
incident
going
on,
but
that's
what
I
had.
A
A
It
was
a
really
helpful
session
kind
of
walking
through,
like
all
the
different
ways,
customers
can
access
the
variables
and
also
what
kind
of
where,
where
we
might
see
people
using
variables
as
Secrets
and
like
kind
of
some
of
those
right
like
behaviors,
that
we
want
to
work
on
correcting,
and
so
it's
it's
a
lot.
A
But
definitely,
if
you
get
the
chance,
you
know
you
can
one
and
a
half
2x
beat
it
and
Empower
through
it,
because
it
does
show
like
a
lot
about
like
oh
here
are,
like
the
you
know,
five
different
places
people
can
make
updates
to
variables
and
and
I
think
like
there's.
Definitely
a
lot
of
reason.
A
Why
there's
confusion
around
variables
and
precedence
and
so
longer
term,
like
we
might
even
consider
like
how
do
we
wanna,
let's
say
clean
up
the
rules
Maybe,
because
yeah
I
can
I'm
looking
at
the
examples
and
I
can
see
why
people
are
confused.
B
Yeah-
and
that
made
me
wonder,
like
there
are
many
improvements,
and
we
of
course
have
many
issues
that
are
existing,
but
I
mean
when
we
were
doing
this
benchmarking
study
for
the
teams
in
verify
at
this
point,
I
would
say:
there's
nothing.
That's
of
like
a
very
high
value
to
us
from
that
study
that
we
can
start
focusing
on.
So
would
you
consider
like
I,
don't
know
what
the
plan
is
just
like?
What
would
we
have
our
own
benchmarking
study
going
forward.
A
I
think
we
should
consider
it.
My
understanding
is
there
probably
is
some
stuff
out
there
like
not
necessarily
A
benchmarking
study,
but
I.
Think
Jackie
had
alluded
to
a
couple
of
other
link
bits
of
research,
so
we
should
see
what's
in
there
first
and
then
we
probably
should
really
think
about
a
study.
If
we're
going
to
make
I'll
say
maybe
some
like
larger
changes
like
one
of
the
things
we
talked
about
in
our
one-on-one
was
like
why?
A
Why
can
you
set
variables
and
like
the
settings
page
right
like
some
of
those
things
and
that's
something
new
and
I
talked
about
as
well,
which
is
like
it
doesn't
make
sense,
but
like
people
now
know
where
it
is,
you
know
how
do
we
kind
of
like
change
that
and
I
mean?
Are
we
giving
people
too
many
places
to
go
and
set
their
variables
in
general,
like
because
there's
a
lot.
B
Yeah
yeah
definitely
so
there
is
a
lot
that
that's
what
I
was
also
like
thinking
about
that
there's
a
lot,
but
how
do
we
know
which
one
we
should
like
really
focus
on.
A
Yeah
and
then
like
I
mean
maybe
we
can
think
about
it
differently,
like
custom
variables
versus
like
the
predefined
ones
right
like.
Maybe
we
can
give
people
more
flexibility
with
the
custom
ones,
but
like
the
predefined
ones,
maybe
need
a
little
more
I.
A
Don't
know
Aussie
control
right,
because
if
it's
a
predefined
variable
like
why
are
people
always
overwriting
the
values
like
that
doesn't
make
sense
to
me,
like
the
more
I
think
about
it,
the
less
that
makes
sense
to
me
so
I
think
like
maybe
we
can
dice
it
up
into
different,
like
maybe
we
need
to
look
at
variables
and
say
what
are
all
the
different
kinds
or
use
cases
and
then,
like
kind
of
start
from
there
like
I,
don't
we're
not
going
to
fix
variables
overnight.
B
Right
and
the
issue
that
that
I
was
recently
looking
at,
which
was
like
sort
of
giving
a
parity
in
treatment
in
the
visual
treatment
of
the
two
tables
for
variables,
I.
B
Think
right
now
we
have
agreed
on
keeping
the
scope
of
the
issue
really
small
and
I
think
once
the
vibration
happens
to
Wu,
we
should
be
conducting
a
research
first
and
then
getting
to
other
issues,
because
I
also
saw
that
there
are
some
very
conflicting
issues
which
are
existing
in
a
parallel
like
this
is
good,
but
the
other
one
says:
oh,
no.
This
is
bad
fix
it,
so
we
definitely
need
our
research.
A
Yeah
I
think
we
need
to
really
like
dig
into
like
some
of
these
different
use
cases
because
yeah
there
is
they're
all
over
the
board
yeah
or
like
no.
This
proposal
works
better
for
me
like
okay,
let's,
let's
talk
this
through
and
then
we
had
a
community
contribution
for
another
predefined
variable
this
past
week
and
it's
like
dude.
A
We
have
a
lot
of
predefined
variables,
so
I
think
we
do
need
to
like
spend
some
time
and
just
like
figure
out
like
kind
of
what's
a
more
clean
way,
and
how
do
we
deal
with
things
like
inheritance
of
the
variables
and
like
who?
And
when
should
people
be
allowed
to
make
any
of
those
changes
right?
A
So
it's
there's
a
lot,
not
gonna
lie,
but
yeah.
It
was
definitely.
It
was
like
a
like,
like
waterfall
of
like
information
this
morning,
so
yeah
lots
on
variables
and
I'm
trying
to
decide
if
we
want
to
actually
break
variables
out
as
its
own
category,
and
my
thought
there
is
just
because
right
now
it's
a
feature
of
Secrets
management,
but
like
we
also
kind
of
want
to
discourage
our
customers
from
using
variables
or
Secrets.
A
A
Cool
I'll
write
that
down
now
and
but
yeah
did
either
of
you
have
anything
that
you
wanted
to
cover.
A
C
A
All
right,
awesome
and,
let's
see
bethica
you'll,
have
your
design
issue
ready
to
go
I'll.
Do
our
recording
next
week
we'll
see
how
the
feature
change
lock,
effects.
What
rolls
over
to
160
in
terms
of
the
back
end
work
but
yeah.
Otherwise
we
will
I
will
start
doing.
The
group
tagging
on
the
on
the
issue.
C
A
Okay,
I
thought
that
it
was
an
accident
that
all
the
stuff
was
under
the
was
under
the
read-only.
C
A
lot
of
them
are,
they
do
have
recordings,
but
so
I
was
like.
A
Awesome
all
right
and
I
will
also
link
the
product.
Direction
showcase
I,
don't
know
I,
know,
I
saw
it
in
the
op
slack
Channel,
but
I
don't
know
if
it
made
it
to
ours.
So
I'll
I'll
make
sure
that
that's
visible
but
I
rambled
for
a
bit
about
what
I
think
our
our
team's
direction
is
both
short
and
long
term.