Every time someone asks me how I like working at GitLab, I say, "I love it here!" With our company culture, 100 percent remote workforce, and growing team, it's a pleasure to work with such a high energy team. The security department is continually growing – very fast! We each have our own specialties and bring a diverse selection of strong experiences, while working very well together. In my position, I have been focusing very heavily on policy as code to raise the bar in security here at GitLab. This blog post was inspired by William Chia's Google Next 2018 recap. If you haven't read it, I highly recommend it!
Security highlights of Google Next 2018
I was excited coming into this conference for Forseti, especially with the announcement of Forseti 2.0. We had a Forseti Hack Day that kicked off a day before the actual conference, which allowed me to interact with Google engineers, product managers, and Forseti customers. For anyone who missed Forseti's session from Chris Law, Michael Capicotto, and Marten Van Wezel, you can check it out the recording. See the details for joining the discussion here.
"Istio is platform-independent and designed to run in a variety of environments, including those spanning Cloud, on-premise, Kubernetes, Mesos, and more." I'm excited to see Istio 1.0, which was just released a few days ago! See the team's talk from Tao Li and Samrat Ray.
Everyone can use best practices. At Forseti Hack Day, I met Tom Salmon who has vast experience in security. In his talk, he provides a great knowledge base and reference point to best security practices in GCP.
Sessions are now live
These were only a few sessions at Google Next, and there are hundreds of others to check out. You can find them neatly categorized on YouTube.
We'd love to hear your feedback
We'd love to hear from you on how you use any of these products in your environment. Our team is currently working very closely with the Forseti team, and I'm sure they would love to have you join in on the discussion as well. Don't hesitate to reach out directly to me by email (email@example.com) or join any of these groups to keep a dialogue going about any of these products. We can only help each other in the process.
“A GitLab team-member's security track recap of #GoogleNext18” – Jim Thavisouk
Click to tweet