►
From YouTube: Education SIG (October 5, 2022)
Description
Meeting minutes: https://docs.google.com/document/d/1Lt8uGpiMFfgws8VF36xtTMaJAeHufha-7Dqz1tjrPGY/edit
A
All
right
team,
it's
a
couple
minutes
after
the
hour,
welcome
to
the
October
5th
edition
of
the
education
Sig.
We
have
a
couple
exciting
things
to
talk
about
today.
Please
Mark
your
attendance
in
the
agenda.
If
you
have
any
opens,
please
add
those
below
the
agenda
section
and
first
off,
as
is
tradition,
do
we
have
any
new
friends
that
wanted
to
introduce
themselves
to
the
group
and
say
hello.
A
All
right
do
we
have
anyone,
that's
interested
in
helping
taking
notes,
critical
part,
more
important,
I
think
the
most
important
role
of
the
day
I
can
jump
in
on
that
awesome.
Thank
you,
Kara.
Thank
you.
Dave
everyone's
welcome,
but
I
say
it's
most
important
because
we
do
have
a
lot
of
people
that
are
interested
in
this
group,
and
people
do
flip
back
if
they
miss
a
call
and
look
through
the
meeting
notes.
So
they
are
very
helpful
to
those
that
don't
show
up
all
right.
A
A
B
A
Us
just
under
two
months
to
finish
our
revisions,
and
hopefully
that
means
we
can
get
started
on
actual
education
stuff
more
quickly
and
then
I
will
talk
about
the
spreadsheet.
So
now
I
will
turn
it
over
to
our
sub
team
leaders,
we'll
start
off
with
Dave
Russo.
Do
you
want
to
give
us
a
brief
update
on
how
section
one
is
doing
and
do
you
think
December
1st
is
an
awesome
date?
You'll
get
done
by.
C
I
think
December
1st
is
an
awesome,
Target
date
for
us
to
strive
for
we'll
see
what
we
can
do.
I'll
get
some
links
in
in
the
update
that
I'm
typing
in
right
now
momentarily,
but
last
meeting
we
talked
a
lot
more
in
depth
about
goal
1.1,
which
is
reviewing
existing
educational
materials
that
are
out
there
and
how
we're
going
to
collect
this
information
and
organize
it
and
then
subsequently
we're
going
to
plan
to
do
a
survey
to
determine
what
might
be
missing
or
what
we
might
need
to
focus
on.
C
C
So
I
ask
everybody
to
continue
to
solicit
your
friends,
your
family,
your
pets,
whoever
might
know
this
information
put
it
into
that
working
document.
We
also
put
a
spreadsheet
together.
Crow
put
a
spreadsheet
together,
we're
using
to
help
figure
out
what
the
organization
is
we
did.
The
team
is
contributing
to
the
whole
thing.
Crow
put
a
lot
of
effort
in
putting
that
initial
spreadsheet.
C
Together,
I
wanted
to
thank
you
for
hundreds
of
hours
and
all
seriousness,
we're
trying
to
figure
out
the
best
way
to
organize
and
categorize
the
materials
that
are
out
there
once
we
have
them
identified.
This
is
going
to
be
vital
for
us
as
we're
going
through
specifics
in
the
plans
to
figure
out
what
kind
of
training
is
available
where
to
point
people
for
specific
types
of
training
and
ultimately,
what
the
level
of
level
of
training
might
be
appropriate
for
certain
material.
B
B
D
Everybody
yeah,
yeah
I
think
it
would
be
best
if
Randall
gave
a
brief
update,
because
I
wasn't
present
in
the
the
last
one.
Due
to
circumstances
I
saw
we
updated
the
the
calendar
notion
correctly,
because
I
was
really
confused,
so
I
couldn't
be
there
so
Randall.
Would
you
be
so
kind
to
give
a
small
update
about
it?.
E
So
yeah
I
I
was
multitasking,
but
we
had
we
had
so
we
have
some
interesting
stuff
going
on
in
SKF
we're
doing
kind
of
preparing
SKF
to
get
be
at
the
level
where
we
could
like
mess
with
it
and
add
more
stuff
to
it.
So
we're
kind
of
dealing
with
the
stuff
that
we
have
now
we're
we're
talking
about
doing
a
back-end
redesign
in
k-native
and
also
we've
been
talking.
We've
been
Gathering
some
designers
to
do
a
front-end
redesign.
E
So
you
have
four
people
on
the
front,
end
redesign
and
so
far
we
have
about
five
people
and
the
developers
that
I've
been
able
to
gather
out
of
my
AI
doings
and
then
the
next
part
we've
been
really
trying
to
clarify
like
what
our
goals
are
for
and
what
our
expectations
are
with
SKF,
because
SKF
is
a
great
big
platform.
So
we've
been
kind
of
trying
to
clarify
that
so
that
we
can
use
that
something
as
like
our
guiding
principle
in
this
redesign
so
yeah.
Basically,
that's
as
far
as.
B
B
A
And
I'll
ask
Glenn
and
Randall
the
same
question:
I
asked
Mr
Rousseau:
do
we
think
we
can
have
the
plan
refined
and
fleshed
out
by
December
1st
so
that
we
can
get
that
presented
to
the
governing
board
and
it
doesn't
stop
any
work
on
SKF
or
any
surveys
or
anything
else?
But
can
we
get
the
plan
written
out
by
December.
F
E
A
A
A
line
item
saying
SKF
enhancements
and
have
a
swag
for
resource
needs
and
a
time
estimate.
That's
fine.
I,
don't
need
the
SKF
plan
in
detail,
but
I
need
something
to
give
the
governing
board
before
the
end
of
the
year,
so
that
we
can
know
if
we're
going
to
get
funding
or
if
they
require
any
changes.
E
A
Yeah
and
it's
the
conversation
you
and
I
had
with
art
the
other
day
for
the
other
Sig,
it's
you
know,
I
need
to
have
the
Milestones
laid
out
and
again
those
estimates
for
any
resources
over
time
or
costs
got
it
and
again
that
doesn't
hinder.
If
people
actually
want
to
start
working.
That's
awesome,
don't
we
can
do
all
this
in
parallel,
but
I
need
to
have
that
physical
document.
You
know
to
print
out
and
hand
to
Mr
bellendorf
here,
yeah.
F
D
Want
to
raise
because,
of
course,
we're
also
heavily
defended
not
only
about
the
work
they
want
to
do
in
SKF
and
all
that
good
stuff,
but
also
about
the
materials
right.
I
I
know:
Randall,
you've
been
busy
doing
a
sort
of
Gap
analysis
and
based
on
what
we
should
derive
at
a
material
Zone,
the
the
web,
API
and
all
the
good
stuff,
but
I
think
there
was
also
a
bit
tied
together
with
the
set
one
if
I
remember
correctly,
yeah
and
based
on
on
that
outcome
as
well.
A
Yeah,
we'll
start
that
in
about
10
minutes,
I
will
tell
you
you
will
not
have
a
hundred
percent
accurate
list
of
everything
to
do
so.
I'm
going
to
need
you
to
provide
an
estimate
as
best
we
can
and
then,
under
with
the
understanding
we
may
need
to
Pivot,
we
may
need
to
come
back
for
a
secondary
request
once
we
have
mostly
complete
knowledge.
D
Maybe
another
question
as
well:
is
it
allowed
in
the
Milestone
definition
to,
for
example,
Define
I,
don't
know
15
or
20
unknown
like
hey?
This
is
what
we
think
it
should
be,
but
we
would
like
to
have
a
bit
more
because
you
know
the
material
and
content
can
actually
yeah
be
more
important
than
we
actually
chewed.
D
D
A
B
A
It
is
going
to
look
like
a
combination,
the
child
of
that
and
what
we
have
in
git.
So
my
intention
is-
is
to
take
some
of
the
pros
from
the
plan,
potentially
change
that
and
that's
something
that
I'll
probably
set
up
a
call
with
the
working
group
lead.
The
stream
leads
to
do
to
do
the
pros,
and
then
we
will
take
these
GitHub
sections
and
recombine
them
into
you
know.
One
document.
A
E
E
F
F
My
colleague
Michael
is
on
the
is
on
the
line
as
well,
and
we're
and
he's
he
he's
working
specifically
in
the
in
the
developer,
education
kind
of
part
of
the
business,
and
so
so
yeah
like.
Where
is
this?
How
is
this
work
being
organized?
I?
Guess
is
my
question
because
I
didn't
know
there
was
a
PR
up
until
Randall
said:
there's
a
PR,
so
is
there?
Is
it
happening
on
the
mailing
list?
Is
it
happening
on
in
slack?
F
A
A
E
We
just
we
just
I
just
started
a
group
I
just
oh
I
just
started
a
group
chat
with
avishay,
then
yeah
we
just
basically
what
we
did
is.
We
ended
up
splitting
up
like
organizations
but
Dan
I.
We
could
right
now
it's
all
being
organized
and
avishays,
like
Fork
of
the
Sig,
repo
or
working
group.
Repo,
it's
all
being
organized
on
slack,
is
also
yeah.
F
A
A
I
had
a
conversation
with
the
TAC
yesterday
and
the
TAC
agreed
that
things
like
a
foundation-wide
glossary,
dictionary,
lexicon
and
also
things
like
personas
impact,
multiple
working
groups
and
work
streams
within
the
foundation,
so
they
have
agreed
to
create
a
centralized
repository.
So
once
we
are
ready,
we
can
transfer
any
work.
We
do
into
a
a
future
foundation-wide
repository
instead
of
it
being
squirreled
away
inside
this
sig,
so
it'd
be
kind
of
a
top
level
repo.
Potentially,
let
me
go
to
Mr
Russo
first
and
then
Randall.
C
A
I,
don't
have
an
expectation,
I,
don't
see
it
as
a
blocker
for
us
necessary
for
this
group
necessarily
I
think
we're
going
to
need
to
have
once
we
get
our
education
and
cyber
security
things
in
there
and
we
get
the
vulnerability
team
to
get
the
CBD
things
in
there.
I
think
we
need
to
go
approach.
The
other
working
groups
like
supply
chain,
for
example.
They
have
specific
terms
and
meanings,
and
we
want
to
reach
out
to
them.
B
E
I
think
the
the
goal
that
avishay
and
I
had
for
the
record
Dave
was
two
weeks
from
now
to
have
it
all
completed
at
least
the
first
draft,
so
we're
just
copying
and
pasting
and
putting
the
links
in.
So
it's
not
like
it's
a
whole
bunch
of
work.
You
know
yeah
and
and
what
I
was
gonna
say:
Krab
was
what
could
it
be
possible?
Maybe
not
now
I,
don't
know
if
maybe
now
might
be
good,
but
in
the
spirit
of
what
Dan
said,
setting
up
a
slack
channel
for
glossary,
maybe.
A
E
A
B
E
I
just
see
it
getting
like,
because
I
know
we
have
like
application
security
and
then
we
have
like
network
security,
and
then
we
have
like
containers,
which
is
the
whole
thing,
so
I
I
just
I
figure.
That
might
be
better
if
we
had
folders
like
when
for
application
security,
one
for
like
different
things,
but
I
don't
have
I,
don't
know
how
I
would
structure
that
I'm.
Just
saying
that
from
like
a
final
product
level,
having
one
large
thing
that
Dave
do
you
have
input.
A
C
I
I
also
agree:
Kobe
I
have
not
had
a
chance
to
contribute,
so
my
opinion
is
is
what
it
is,
but
I
think
whatever
it
is.
It
needs
to
be
searchable
easily
searchable
and
I.
Think
if
you
start
breaking
these
up
into
folders
you're
going
to
have
terms
that
are
going
to
apply
to
more
than
one
of
those
folders
and
we
don't
want
to
have
multiple
occurrences
of
the
same
term
in
the
dictionary,
so
maybe
tag
things
for
for
what
you're
talking
about
doing,
folders
there's
it
should
be
easily
searchable.
C
D
Glenn
Fair
yeah,
well
indeed,
I
would
say
separating
the
things
and
like
make
the
specific
category
and
folders
make
sense.
I
do
see
the
worry,
but
I
assume
also
that,
for
example,
what
we
will
put
in
to
get
will
need
will
not
be
the
real
searchable
representation
of
the
data
that
we're
going
to
offer
right.
It's
just
for
us
easy.
D
B
A
good
point
yeah,
so
my
my
way
in
on
that
would
be
that
I
would
try
as
hard
as
possible
to
do
it
one
way.
So
it's
exportable
if
we
put
it
into
another
platform,
so
it's
a
lot
easier
to
to
just
run
with
it,
rather
than
doing
it
one
way,
because
it
may
not
be
fully
searchable
now,
but
you
know
if
we
do
it
in
XML
and
tag
it
or
yaml
or
some
other
format
or
just.
However,
we
want
to
do
it
and
then
maybe
it
ends
up
in
a
index.
B
E
That'd
be
great,
I
was
gonna,
say.
If
we
wanted,
we
put
it
in
markdown.
We
could
have
the
GitHub
preview,
but
that
definitely
affects
searchability,
because
the
only
way
to
be
able
to
search
is
GitHub.
So
I
do
think
that,
like
it'd,
be
very
easy
to
make
like
a
one-page
type
thing
or
just
a
search
bar
and
you
put
in
your
term,
and
it
comes
out
with
a
definition.
It
wouldn't
be
that
hard
to
put
something
like
that
together.
F
Glenn
I
just
wanted
to
suggest.
The
important
thing
is,
that
is
the
content,
and
even
if
it's
just
one
markdown
file
glossary.md
that
is
reasonably
uniform
in
its
formatting,
then
it
is
easily
parsable
by
scripts
and
you
can
move
it
into
different
kinds
of
things
and
that's
my
suggestion.
Rather
than
figuring
out
which
color
to
paint
the
shed
agreed.
E
D
D
So
you
can
add
a
new
glossary
item
to
it,
which
creates
in
the
water
a
PR
into
our
repo,
and
indeed
it's
one
biggest
glossary
MD
file
sounds
awesome,
but
you
know,
let's
put
that
in
the
cicd
pipeline
of
GitHub,
where
it
also
generates
a
file
like
that.
Based
on
all
the
separate
categories,
I
mean
it's
way
easier
to
have
group,
yours,
add
new
stuff
to
it,
Etc
and
then
yeah
trying
to
work
in
one
big
as
well.
D
A
If
you
could
send
a
message
out
to
the
mailing
list
today
for
this
sig
and
ask
for
opinions
on
a
name
and
maybe
give
a
due
date
by
Friday,
we
can
I'll
send
a
note
out
to
Jory
to
get
a
slack
Channel
set
up
so
that
we
can
start
to
organize
around
this
particular
task
and
two
pieces
of
guidance.
I
would
give
this
group
is
watch
out
and
try
to
avoid
situations
where
you're
going
to
introduce
rework
or
a
ton
of
additional
future
maintenance.
A
So
try
to
avoid
situations
where
you're
going
to
have
somebody.
You
know
that's
their
job
to
kind
of
caretake
a
file
for
a
while,
and
then
I
forgot
that,
oh
wherever
possible.
We
don't
want
to
be
the
author
of
these
definitions.
There
are
many
great
places
that
already
have
authoritative
definitions,
missed
ISO,
o
wasp
IEEE,
so
wherever
possible,
leverage
somebody's
work
and
if
we
need
to
make
an
adjustment
to
that,
we
can
note.
You
know
this
is
what
IEEE
says
about
this
term,
and
here
is
how
we
modified
that
for
our
working
definition.
E
We
kind
of
we
kind
of
got
to
that
sure
we
got
to
the
mer
how
the
merging
is
going
to
be
a
problem.
So
this
is
what
I
was
going
to
ask,
though
so,
would
it
be
better
to
just
maybe
copy
definitions
and
because
we've
decided
that
we're
going
to
need
like
a
a
way
of
searching
and
displaying,
which
is
not
difficult,
but
maybe,
when
you
put,
for
example,
finder,
because
that
was
one
of
the
terms
we
have
in
there
you
get
what.
E
A
Yeah
yeah
and
again
we
we
can
pivot.
We
can
change
in
the
future,
but
I
would
again
think
about
the
technical
debt,
we're
incurring
by
writing
thing
authoring
things
ourselves
agreed
okay,
fair,
and
we
want
to
make
sure
that
this
is
an
artifact
that
survives
all
of
us
into
in
the
community.
So
we
don't
want
to
right.
A
A
I,
don't
need
this
finalized
today,
but
I
would
like
everybody's
feedback
on
The
Matrix
tab
and
the
xref
tab,
so
the
Matrix
tab
is
once
we
agree
on
how
this
is
organized.
What
information
we
want
to
share
several
of
us
are
going
to
go
through
and
take
you
know:
Randall's
SKF
analysis,
Wheeler's,
fundamental
class
and
then
Dave
has
an
exhaustive
word
doc
of
sources.
So
once
we
agree
upon
what
information
we
want,
we'll
start
to
load
all
that
into
this
spreadsheet.
A
So
we
can
start
to
do
that
inventory
and
understand
what
our
current
assets
are
and
then
we
can
do
the
Gap
assessment
of
where
we
might
need
to
make
invest
in
future
content,
so
think
about
or
providing
opinions.
Now
what
columns
you'd
like
to
see
so
right
now
we're
listing
The
Source?
What
type
of
content
it
is?
Is
it
a
class?
Is
it
a
website?
Is
it
a
Blog
we're
going
to
do?
Is
it
related
to
a
stack
or
language?
A
What's
the
overall
theme
like
cryptography
or
threat
modeling
or
endpoint
security
that
type
of
deal
we're
going
to
list
the
learner
level
like
this?
If
this
training
or
this
artifact
is
targeted
towards
beginners
and
intermediate
people
are
experts
and
all
of
that,
all
of
those
little
drop
downs
are
sourced
by
the
xref
tab.
So
once
we
agree
upon
what
columns,
how
we'd
like
to
organize
it,
I
need
to
get
accurate
representation
of
you
know
how.
We
would
like
to
organize
that,
as
shown
in
the
xref
tab,
Christine.
B
This
is
a
comment
on
the
X
ref
tag.
Perhaps
you
could
maybe
explain
a
little
more.
What
are
the
differences
between
some
of
the
content
types,
because
some
of
them
might
feel
the
same
like
presentation
or
conference
talks,
Hands-On
Labs,
interactive
courses
and
Labs
so
either
might
help
to
get
an
idea
of
what
each
of
them
means
to
you.
So.
A
Right
now
it
is
a
combination
of
four
things:
I
wrote
down
and
then
contributions
from
the
substream
one
suggestions.
People
have
had
so
I
have
not
gone
through
and
vetted
or
normalized
things
yet.
So,
if
you
feel
that
things
are
duplicative,
put
a
comment
or
change
it,
this
is
not
the
finalized
list
yet,
but
I
need
to
get
this
finalized
before
we
start
cramming
and
categorizing
things
into
the
first
sheet.
So
please
please,
please
provide
me
that
feedback
around
these
columns-
and
we
probably
yes
need
to
Define
what
we
mean
by
a
class.
B
C
A
This
is
all
stuff
I've
pulled
out
of
the
air
or
through
sources
that
I
have
used
in
the
past
and
then
Judy
from
Judy
Kelly
from
Red
Hat
has
been
contributing
a
lot
of
ideas
so
again,
if
anyone
has
anything
either
directly
type,
it
in
feel
free
to
change
it
or,
if
you're
hesitant
to
change
it.
But
it
is
a
comment
you
know.
I
feel
this
is
confusing
or
is
duplicative
of
something
else.
A
E
I
kind
of
wanted
to
just
say
so,
I
think
that,
with
like
the
back
end,
the
intention
that
we've
been
leaning
towards
is
having
something
where
that
supplies
all
the
information
like.
So
you
can
integrate.
It,
however,
way
you
want
so
to
give
people
so
like
yeah,
that's
kind
of
how
I
think
it
all
kind
of
come
together,
because
we
host
a
lot
of
information
at
SKS
and
I'm
know
that
we're
going
to
be
adding
a
lot
of
information
as
well.
A
The
intent
of
this
spreadsheet
is
to
get
an
inventory
of
what
is
available,
evaluate
what
we
need
to
do
with
that.
You
know:
can
we
incorporate
it
into
existing
materials?
Can
we
just
wholesale
use
it
or
do
we
need
to
create?
Do
we
have
gaps?
We
have
material
on.
So
this
is
something
a
tool
we're
going
to
use
to
make
decisions
on
future
course
content,
whether
it's
you
know
updating,
David's
class
or
it's
making
podcasts
or
going
to
conferences
we
just
kind
of
need
to
decide.
E
It
did,
but
without
what
I
was
getting
more
at,
is
so
like
when
I
talked
to
David
David
was
talking
about.
How
are
we
going
to
break
this
down,
because
that
relates
to
the
spreadsheet,
because,
like
your
Matrix
spreadsheet,
would
somewhat
suggest
that
you're
tracking
things,
by
course,
which
kind
of
gets
somewhat
difficult,
because
then
you
have
things
like
the
off
swap
testing
course,
which
fulfills
multiple
like
roles?
If
that,
if
you
or
goes
through
multiple
Industries,
if
that
makes
sense,.
A
E
A
So
I
don't
want
to
spend
the
next
six
months
defining
the
list.
We
have
to
have
start
taking
action,
so
this
is
a
first
stab
at
trying
to
roughly
containerize
these
things
so
that
we
can
start
to
understand
how
we
want
to
move
forward.
So
if
we
just
list
SKF,
it's
a
Hands-On
lab,
that's
probably
good
enough
for
now
and
then,
if
we
need
to
refine
in
the
future,
we
definitely
can
pivot
Glenn,
Glenn
and
then
I.
E
D
D
D
A
B
D
I
mean
you
know,
it
feels
a
bit
like
we're
Reinventing
the
wheel
for
the
content
team,
because
I
see
indeed
a
lot
of
items
here
that
are
directly
also,
for
example,
in
the
ascso,
then
I
would
say
hey
if
you
really
want
to
cover
from
A
to
Z.
Let's
use
the
category
items
from
the
asvs
because
yeah
that
that's
what
people
will
pass
I,
don't
know
10
years
been
thinking
about
what
should
be
in
there.
So
I
think
using
that
as
a
guide
and
then
also
for
a
gap.
D
Analysis
would
be
good
and
indeed,
like
Randall's
saying
we
can
correlate
them
hey
these.
Actually,
we
have
material
for
David
available.
Here
we
have
Labs
that
we
can
connect
blah
blah
blah
I,
think
we
we're
doing
it
a
bit
more
correct
or
in
terms
of
completeness,
if
we
add
those
as
well.
In
my
opinion,
I.
A
D
A
B
Or
no
yes,
hi
I
mean
I'm.
Sorry,
this
is
stupid,
but
I'm
still
trying
to
figure
out
what
the
criteria
you
know.
What
does
it
take
for
some
content
to
qualify
and
and
I'll
be
honest,
I
mean
we
have
a
lot
of
content
at
IBM.
We
have
a
lot
of
Education
material
in
the
security
space
and
but
at
the
same
time
I
don't
think
you
know
I,
don't
know
that
we'll
be
able
to
just
contribute
the
whole
content
for
the
group
to
reuse
as
is
and
do
whatever
they
want
with
it.
A
A
Some
of
these
things
we
might
ask
you
know:
I
I
am
in
conversations
with
the
Intel
training
people
about
Intel
donating
some
of
our
secure
development
content.
I
know
that
that
Jeff
has
taken
a
similar
path
within
IBM,
but
worst
case
we
might
be.
The
group
might
be
able
to
see
that
content,
so
it's
shared
with
us
that
we
could
look
at
it
and
then
you
know
write
our
own
if
there
are
gaps
potentially.
So
if
it
is
an
asset,
we
think
we
could
realistically
use.
A
C
So
for
for
Glenn,
specifically
I
see
he's
typing
stuff
in
if
you
could
also
drop
a
comment
about
where
you
got
this
from,
and
why
you
think
it's,
it
might
be
a
better
course
of
action
to
go
with
those
categories.
That'll
be
good
context
for
us
when
we
take
a
look
at
it,
but
it
at
risk
of
beating
this
dead
horse
even
more.
This
is
all
about
right
now.
How
we're
going
to
organize
this?
That's
all
we're
trying
to
to
figure
out
so
please
feel
free.
Let
us
know
what
your
thoughts
are.
C
What
you
think
the
best
way
to
handle
this
is,
it
doesn't
mean
it's
going
to
be
set
in
stone,
but
this
is
how
we're
going
to
proceed
moving
forward.
Initially,
we
have.
We
have
to
figure
out
a
way
to
organize
and
categorize
this
material,
so
we
can
then
do
all
these
other
cool
things
that
we
want
to
do
down
the
road
yeah.
E
So
what
what
asvs
is
it's
basically
like
a
curriculum
of
what
you're
you
should
do
so
I
think
what
Glenn
is
saying.
I
agree
with
this,
that
this
is
what
he's
saying
that
perhaps
we
should
develop
somewhat
of
a
curriculum
before
we
actually
start
evaluating
like
whole.
Subject
matters
because
also
tying
in
with
our.
What
our
no
was
saying
was,
if,
like
asvs
has
specific
requirements
that
you
need
to
fit
that
have
been
they're
very
well,
very
well
elaborated,
there's
actually
like
an
off
swap
working
group,
that's
specific
to
asvf
so
like.
E
Basically,
we
can
take
things
and
I
actually
would
even
argue.
It
would
be
easier
to
address
the
content
if
we
actually
had
like
a
curriculum
that
we
have
to
address.
If
that
makes
sense,
because
it's
really
hard
like
that's
what
I
ran
into
already
in
organizing
SKF,
is
that
when
you
start
to
mobilize
the
courses
as
entire
courses,
it
becomes
a
lot
more
difficult,
because
there's
a
lot
of
overlap.
C
B
Just
on
that
topic
of
curriculum
I've,
you
know
I've
been
attending
meetings
for
a
couple
months
now,
but
I'm
not
sure
if,
before
that
point,
what
were
there
discussions
about
specific
learning
goals
like
you
can't
create
a
curriculum
until
you
know
what
the
learning
goals
are
and
no
okay,
so
that
hasn't
been
discussed.
We.
E
Well,
well,
let
me
say
that
they're
what
I
believe
in
Glenn
can
inform
us
more
I
believe
that
off
swap
did
have
those
meetings
but
like
yeah,
like
all
swab,
has
it
like
it's
been
around
for
a
while.
So
it's
kind
of
become
like
this
Behemoth
of
of
like
knowledge
so,
and
especially
right
now
as
it
relates.
It
relates
all
to
application
security
for
the
most
part.
So
anything
else
there
mobile
is
covered
to
some
degree,
but
anything
else.
Basically,
like
iot
was
pointed
out.
E
A
So
to
Kara's
question:
other
groups
may
have
done
that
this
particular
effort
has
not
done
that
yet
and
I
think.
That
is
something
excellent.
We
probably
need
to
get
written
into
the
plan,
and
that
might
be
a
section
one
thing,
since
it
appears
to
be
rather
fundamental
to
before
we
start
doing
things.
We
want
to
make
sure
we
have
some
objectives:
we're
trying
to
achieve.
First.
B
Cara,
so
I
just
had
one
more
thing
on
that
we've
been
thinking
about.
If
we're
thinking
about
learning
goals,
have
we
discussed
where
the
potential
audience
is
starting?
What
sort
of
knowledge
we
assume
they
have?
What
we
assume
they
don't
have
a
presumably
we're
going
to
have
multiple
potential
audiences
has
any
of
that
been
defined
yet.
A
Well,
you
missed
that
fun
conversation
months
back.
The
answer
is
kinda,
so
in
general
that
if
you're
looking
at
the
xref
tab,
we
have
a
target
audience
that
generally
is
kind
of
a
Persona
we're
targeting
we
have.
We
don't
have
those
fully
defined
yet
or
fleshed
out,
but
those
are
generally
the
categories
of
people.
We
think
we're
going
to
Target
that
will
need
to
tailor
content
for
and
then
we
have
the
lure
level.