Skip to content
Why Cloud Native, API Centric Apps Require Built-In Security, Lacework episode artwork

EPISODE · Oct 23, 2019 · 21 MIN

Why Cloud Native, API Centric Apps Require Built-In Security, Lacework

from DevOps Chat · host DevOps.com

In the traditional datacenter world, security was (or is) very network-centric. Firewalls, IDS, Network Access Control, focus on the aggregation of all traffic traversing in, out, and across the network. Cloud-native applications rely upon different constructs and methods of building applications. It's not just the software and technology stack that requires different security in the cloud-native era. We can't just surround cloud-native applications with security; we must build in security. And to do that requires you understand how container and microservices applications are made using DevOps. You must think about how DevOps works to build in security properly. Enter Lacework, a platform built for DevOps teams to build security into cloud-native applications. Vikram Kapoor, Lacework Co-Founder and CTO, joins DevOps Chat to explore API-centric applications and infrastructure-as-code. We discuss how to build security into cloud-native applications through the DevOps-based software creation process, and not only rely on runtime security technologies. Vikram also discusses some of the planned uses for the recent $42m round of funding.

Episode metadata supplied by the publisher feed · Published Oct 23, 2019

Embed this episode

Ready to play

Why Cloud Native, API Centric Apps Require Built-In Security, Lacework

0:00 21:34

No transcript for this episode yet

We transcribe on demand. Request one and we'll notify you when it's ready — usually under 10 minutes.

No similar episodes found.

Frequently Asked Questions

How long is this episode of DevOps Chat?

This episode is 21 minutes long.

When was this DevOps Chat episode published?

This episode was published on October 23, 2019.

Can I download this DevOps Chat episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.
URL copied to clipboard!