►
From YouTube: GitLab Low to High Cross Domain Collaboration
Description
Discover how the US Government uses GitLab for collaboration across enclaves, enabling mission critical work among teams with different classifications in disparate locations.
A
Welcome
it
is
a
new
year
and
a
new
season
for
our
tech
leadership
series.
I'm
your
host
Frances
rose
with
the
government
matters,
thought
leadership
network,
we're
kicking
things
off
with
innovation,
it's
more
than
a
buzzword.
It's
a
discovery
or
a
series
of
discoveries
that
result
in
a
more
modern
and
secure
architecture
for
federal
IT
systems.
Today,
you'll
hear
about
some
of
those
discoveries
at
the
Air
Force,
the
National
Institutes
of
Health
Amazon,
Web,
Services,
gitlab
and
great
circle
technologies.
What's
next
for
innovation,
let's
find
out.
A
Open-Source
tools
can
improve
collaboration,
app
development
and
the
speed
of
mission
delivery,
but
the
coding
process
can
look
a
lot
different
if
it
falls
in
the
classified
realm
instead
of
the
unclassified
realm
here.
Our
next
panel
shares
best
practices
for
bridging
those
two
worlds
and
more
Marc
Chris,
a
strategic
leader
of
national
security
programs,
gitlab
Brent
Bercy,
is
president
of
great
circle
technologies.
Gentlemen.
Welcome
thanks
for
coming
on
the
program.
What
does
the
coding
process
look
like?
How
is
it
different
in
a
national
security
or
classified
environment,
as
opposed
to
an
unclassified
environment?
Sure.
B
So
Frances
it's
similar
in
some
ways
in
that
you've
got
a
set
of
developers.
You
typically
have
a
government
program,
manager
or
leader.
You've
got
folks
working
across
a
spectrum
of
what
we
call
the
DevOps
or
development
lifecycle
that
occurs
on
the
unclassified
side
and
very
similar
on
the
classified.
The
challenge,
though,
is
really
around
getting
those
teams
to
be
able
to
communicate
a
lot
of
times
it's
hard
to
find
cleared
developers,
especially
in
the
DMV,
where
we
compete
with
all
kinds
of
high
tech
firms
moving
into
the
district.
A
C
Of
the
biggest
challenges
that
the
government
has
is
that
they
have
massive
data
data
stores
that
are
collected
from
a
wide
variety
of
sensors
people
and
and
different
types
of
technology
and
frequently
there
isn't
a
corollary
in
the
in
the
open-source
community
or
the
open
Internet.
And
so
we
have
a
programs
that
are
focused
on
a
single
source
and.
A
C
A
B
So
one
of
the
best
practices
we've
seen
is
where
government
programs
will
say
well
I
need,
then
a
common
technology
foundation
that
at
least
allows
me
to
seamlessly
work
from
the
low
side
to
have.
My
developers
and
my
program
managers
be
able
to
bundle
up
all
that
hard
work.
They've
done,
move
it
up
to
a
secure
Enclave
and
let
my
team
in
that
secure
Enclave
be
able
to
pick
it
up
without
losing
context.
A
B
It's
both
it's
a
change
in
the
way
organizations
are
doing
business
and
that
changes
is
really
being
driven
by
a
couple
of
challenges.
One
of
them
is
speed
to
mission.
So
the
idea
that,
if
I'm
developing
code
that
what
my
application
in
the
past
Francis,
it
could
be
static
for
years
at
a
time
right.
Well
now,
the
world
is
changing
too
fast
and
the
landscape
that
the
government
has
to
focus
on
is
changing
too
quickly.
A
What
have
you
seen
Brent
as
far
as
collaboration
among
Tina
there's,
a
collaboration
is
tremendously
important
in
that
kind
of
environment
and
in
all
kinds
of
environments
in
this
in
this
subject
area,
what
have
you
seen
as
far
as
effective
collaboration
among
teams
and
the
individuals
within
those
teams?
So.
C
We
sponsored
an
internship
program
when
we
took
unclassified
interns
from
the
the
the
regions
and
the
better
schools
and
their
data
science
programs,
and
we
helped
them
marry
their
innovative
capabilities
with
customers
that
work
in
highly
classified
enclaves
and
we're
able
to
demonstrate
using
this
framework
mission
value
within
just
a
summer.
In
fact,
this
this
last
internship,
we
were
able
to
convince
a
customer
to
continue
those
interns
throughout
the
year
because
they
they
can't
hire
people
with,
have
those
those
particular
schools.
Anything,
and
so
it's
a
it's
really.
A
There
were
there
barriers
or
hurdles
to
overcome
in
getting
customers
who
work
in
a
classified
environment.
To
understand
part
of
your
work
can
be
done
over
here.
It's
not
classified,
and
then
we
can
move
it.
I
mean
that
strikes
me
that
that
that
mental
barrier
might
have
been
the
hardest
thing
to
overcome
for
both
of
your
customers.
It.
B
Really
was
one
of
the
best
practices
is
to
begin
either
for
the
program
leadership
or
for
us
as
technologists
to
begin
working
with
the
chief
information
security
officer
from
the
programmer
or
the
broader
agency,
and
what
happens
Frances.
If
you
get
a
security
officer
that
is
forward,
leaning
and
says
you
know
what
the
the
mission
needs
to
develop
at
a
much
more
rapid
pace,
I'm
willing
to
lean
a
little
bit
forward
with
this
idea
that
more
of
my
application
can
be
developed
on
the
low
side,
or
maybe
it's
as
Brent
mentioned,
it's
a
research
project.
B
C
The
exquisite
data
that
the
US
government
deals
with
and
so
there's
been
a
large
gap.
You
have,
you
know
very
powerful
and
capable
companies,
but
they
just
don't
know
how
to
relate
their
technology,
and
so
the
collaboration
of
teams
is
critical,
because
if
you
can
take
a
subject
matter,
experts
on
both
sides
and
have
them
collaborate
seamlessly
and
not
have
to
worry
about
disclosing
things
that
are
inappropriate.
Then
all
of
a
sudden
amazing
things
count
so.
A
A
I'll
start
with
you
mark
what
are
the
best
practices
for
collaboration,
especially
in
an
environment
where
some
people
know
that
there
are
some
things
that
they
can't
talk
about
with
these
other
folks,
right
I
mean
that
seems
to
me
to
be
the
most
delicate
thing
that
all
of
these
people
are
navigating.
Is
that
fair?
That.
B
First
of
all,
making
us
change
our
culture
to
be
more
agile.
We
we
call
it
agility,
and
one
of
those
drivers
is
that
changing
landscape
of
the
world.
So
having
that
cultural
piece,
first,
okay,
there's
a
critical
driver
and
I
need
to
change
my
culture.
Secondly,
the
collaboration,
then
okay,
maybe
I'm
willing
to
open
up
to
this
idea
that
I
can
collaborate
across
these
silos,
beum
technology,
silos
or
cultural
and
then,
lastly,
what
how
do
I
get
everybody
on
the
same
sheet
of
music?
B
C
So
I
think
part
of
what
makes
that
happen.
Is
this
concept
of
trust
and
illuminating
that
that
trusts?
So
as
we
as
we
go
through
a
process,
if
I
have
somebody
who's
never
talked
to
somebody
on
the
outside,
giving
them
the
tools
and
the
insight
that
allows
them
to
understand
that
the
the
situational
context?
Where
is
this,
this
particular
individual?
A
Apologize
because
they
don't
remember
which
one
of
you
said
it,
but
we've
hit
the
term
dedsec
ops
a
little
bit
earlier
and
that
I
think
it
was
you
Brent
and
that's
shifted.
It
used
to
be
DevOps.
It
is
now
dev
sec,
ops.
What
difference
does
that
make
in
the
context
of
the
conversation
that
we're
having
it.
C
Goes
to
that
point
of
trust.
So,
if
I'm
going
to,
if
I'm
going
to
bring
something
into
my
Enclave
into
my
enterprise,
can
I
trust
it
and
if
it's
a
massive
code
bundle
which
is
traditionally
what
open
source
is
it's
very
difficult
to.
You
know
to
understand
that
there's
lots
of
technology
that
will
scan
that,
but
in
many
instances
you
can't
capture
with
those
tools,
the
intent
behind
the
person.
That's
there
that
changes
and
when
you're
doing
this
in
a
collaborative
way
where
somebody
in
real
time
is
now
contributing
something.
C
So
you
you,
you
don't
have
the
luxury
of
just
scanning
the
code.
You
want
to
understand
the
intent
because
you're
sharing
your
requirements
or
or
feedback
from
from
tests,
so
that
dedsec
ops
framework
is
really.
How
do
we
put
a
wrapper
of
trust
around
the
entire
process?
I
think
that's
the
simplest
way
to
say
and.
B
Sure
so
that
single
foundation
that
we
both
talked
about
so
are
the
technology
that
get
lab
provides,
is
a
single
end
and
Sekhar
platform.
So
what
we've
done
is
brought
in
that
ability
to
have
context
and
therefore
trust
with
teams
working
across
various
enclaves,
so
the
technology
being
a
single
dev,
sec,
ops,
solution
that
covers
all
ten
stages
gives
you
that
ability
to
say
I've
got
everyone
on
the
same
sheet
of
music.
I've
got
built-in
security.
I
can
trust
this
mm-hm
and
now
I
get
the
context
around
everything
and
that
speeds
that
time
Domitian.
We.
A
About
a
little
over
two
minutes,
left
and
I
want
your
feedback
on
this,
both
of
your
feedback
on
this
question.
We've
talked
a
lot
about
the
people,
how
the
people
interact
with
each
other.
What
do
the
successful
people
that
work
in
this
space,
whether
they're
on
the
classified
side
of
the
unclassified
side?
What
do
those
individual
people
look
like?
What
are
their
skill
sets?
What
makes
them
successful?
What
attributes
do
they
have
mark?
You
go
for
sure.
B
So
one
of
the
attributes
is
that
a
ability
to
lean
forward
right,
it's
it's,
it's
a
bit
of
a
risk
taker,
but
it's
risk
within
that
management
framework.
And
so
that's
one
of
the
skills
and
then
the
other
skill
is
you
know
what
I
can
start
by
contributing
even
the
smallest
little
bit
of
contribution,
what
we
call
a
minimal,
viable
change
and
then
my
teammates
can
collaborate
and
iterate
on
that.
So
so
collaboration
and
leaning
forward
and
what
are
the
successful.
A
C
To
speak
in
this
country
and
I
think
herding,
the
cats
is
the
challenge
there.
There
are
a
myriad
of
tools
out
there
and
many
people
are
overwhelmed
and
that's
one
of
the
reasons
why
we've
partnered
with
get
lab,
because
that
that
integrated
workflow
is
key.
It's
very
easy
for
the
customers
to
adapt.
If
they
have
a
few
licenses
they
can,
they
can
take
advantage
of
that,
but
but
the
the
confidence
that
they
have,
this
seamless
workflow
is
simplifying
Brent.