GitLab Security Department, 7 Oct 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: What Does Red Team Do?

Description

Devin Harris (Senior Security Analyst, Field Security - https://about.gitlab.com/handbook/engineering/security/#field-security) and Greg Johnson (Senior Security Engineer, Red Team. - https://about.gitlab.com/handbook/engineering/security/#red-team) discuss what exactly the External Security Communications Team does at GitLab.

Greg mentions several key links which are here:
- https://about.gitlab.com/handbook/engineering/security/red-team-roe.html
- Slack: #security, #security-department

A

Devin: hi,, I'm devin harris a field security analyst here at gitlab and.

A

I'm with greg johnson from the red team. All right would you like to introduce yourself?

A

greg: sure,. My name is greg johnson. I'm a.

B

Senior security engineer on the red team here at gitlab devin: awesome. Well, thanks for.

A

Taking the time to talk to us as you know, we're going to increase security.

A

Awareness and I would like to ask you a couple questions about your team, greg:, okay,.

A

Devin:, so in your own words,, what does the red team do here at gitlab greg:? So in a nutshell,, a.

B

Red team takes the adversarial role in securing gitlab assets and the gitlab.

B

Organization as a whole. at gitlab, you know we operate probably.

B

A little different than most red teams, where we're adversarial, but very.

B

Collaborative and we perform live attacks against gitlab and work closely.

B

Primarily with our secops team, (security operations), but really any and all other.

B

Teams where we can. we operate under a set of rules for engagement, which you.

B

Can find in the handbook if you want to look for it, search for red team rules.

B

Of engagement, so we're not going to be out there hacking your personal devices.

B

Or cell phones, or anything like that, we were mostly targeting gitlab and.

B

Trying to improve security and detection devin: awesome we'll make sure to link to that.

A

In the video, when we're done here, greg:, okay, devin:, what's a cool project.

A

You guys have recently worked on or currently working on, greg:, okay, yeah, we've got.

B

A lot of cool stuff going on red team is fairly new to gitlab as a whole.

B

The the four of us currently there's four team members, including the.

B

Manager, steve, and you know we're in the process of building up the team and.

B

Figuring out how to work effectively together, not only within our own team,.

B

But as within the department as a whole, so it's been really cool to to witness.

B

That and participate in and get things off the ground just from scratch.

B

Basically, and with our first two operations, we're basically trying to.

B

Better understand the attack surface to gitlab from an.

B

Adversaries perspective in this case we're emulating an adversary that is.

B

Performing reconnaissance for a targeted attack on gitlab directly, we.

B

Kind of take a fairly non-traditional approach to this out of the gate, but.

B

We're trying to automate as much of those attacks as we can so that's a very.

B

Improvement, we can replay those attacks without too much effort, devin: awesome,, that's good stuff, and then.

A

Lastly, this may not apply to your team. I know you're, pretty collaborative, but.

A

When, and how would somebody at gitlab get in contact with your team? greg: right now? The easiest way is through slack, you can @red-team mention us.. You would contact us.

B

With questions and concerns about whether something is security related to you know, gitlab directly or.

B

Line of business integral- and you can tag us also in gitlab issues and get help there.

A

Devin: awesome, well, thank you very much for your time today greg. I looking forward more closely with your team.

A

Greg: no problem. Thank you.