{"id":25169,"date":"2022-12-21T23:26:28","date_gmt":"2022-12-21T23:26:28","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/21\/teleport-takes-identity-based-data-security-to-the-next-level-with-code\/"},"modified":"2022-12-21T23:26:28","modified_gmt":"2022-12-21T23:26:28","slug":"teleport-takes-identity-based-data-security-to-the-next-level-with-code","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/21\/teleport-takes-identity-based-data-security-to-the-next-level-with-code\/","title":{"rendered":"Teleport takes identity-based data security to the next level with code"},"content":{"rendered":"

<\/a>\n
<\/p>\n

\n

As infrastructure as a service opened the doors for infrastructure as code, developer teams started to use programmatic APIs to spawn new resources quickly, and on demand. Boosted by scalability and automation, the IaC approach strengthened DevOps teams, but the rapidity of application iterations ofent left security teams justifiably concerned.<\/p>\n

The solution: applying the IaC mindset to data protection, crafting a method to support security and policy as code. Now DevSecOps teams can automate tasks such as pen testing, curbing infamous delays in production time.<\/p>\n

\u201cIf you want to have a set of rules that govern who or what and when, and under what circumstances can access what data\u2026 wouldn\u2019t it be nice to use code for it? Teleport does [that] with policy.\u201d said <\/span>Ev Kontsevoy<\/span><\/a> (pictured), co-founder and chief executive officer of Teleport (Gravitational Inc.) \u201cSo essentially, if you want security as code, that\u2019s what Teleport provides.\u201d<\/span><\/p>\n

Kontsevoy spoke with theCUBE industry analyst <\/span>Savannah Peterson<\/span>\u00a0and John Furrier<\/span>\u00a0<\/span>at AWS re:Invent, during an exclusive broadcast on theCUBE, SiliconANGLE Media\u2019s livestreaming studio. They discussed identity-native and security-as-code trends.\u00a0(* Disclosure below.)<\/em><\/span><\/p>\n

The following has been edited for clarity.<\/p>\n

Peterson: Teleport is about identity, right? Give us a little bit of a pitch.\u00a0<\/b><\/p>\n

Kontsevoy: Teleport is the first identity-native infrastructure access platform. It\u2019s used by engineers and by machines. First, identity-native. What does it mean? Identity-native consists of three things. The first component of identity-native access is moving away from secrets toward true identity. By secrets, I mean things like passwords, private keys, browser cookies, session tokens, and API keys. All of these things are secrets, and they make you vulnerable\u2026 We use something called True Identity; it\u2019s a combination of your biometrics as well as the identity of your machines. That\u2019s [trusted platform modules, hardware security modules, YubiKeys], etc.\u00a0<\/span><\/p>\n

The second component is zero trust. Teleport is built to not trust the network. So every resource inside your data center automatically gets configured as if there is no perimeter. It\u2019s as safe as it was on the public network. And the third one is that we keep the access policy in one place. So, Kubernetes clusters, databases, [remote desktop and all of these protocols], the access policy will be in one place.<\/span><\/p>\n

Peterson: How much more secure is leveraging biometric data for identity than the secrets we\u2019ve been using historically?\u00a0<\/b><\/p>\n

The fact is that I don\u2019t see how your credentials will be stolen in this system simply because your TPM on your laptop and your fingerprint cannot be downloaded. A lot of people ask us a slightly different question; it\u2019s almost the opposite of it. Like how can I trust you with my biometrics? When I use my fingerprint, that\u2019s my information; I don\u2019t want my company to get my fingerprint.\u00a0<\/span>The answer to that question is, your fingerprint doesn\u2019t leave your laptop. Teleport doesn\u2019t see your fingerprint.\u00a0<\/span><\/p>\n

Furrier: What are your conversations with customers at re:Invent? Because this is a much broader conversation on the architectural refracturing of organizations.\u00a0<\/b><\/p>\n

Kontsevoy:\u00a0<\/span>I will mention two trends I observed.<\/span>\u00a0<\/span>The first one is not even security related.<\/span>\u00a0<\/span>It\u2019s basically how, as the cloud becomes more mature,<\/span>\u00a0<\/span>organizations<\/span>\u00a0<\/span>develop their own internal ways of doing cloud properly.<\/span>\u00a0<\/span>And they\u2019re not the same.<\/span>\u00a0F<\/span>or example,<\/span>\u00a0some companies love having,<\/span>\u00a0<\/span>ideally, just one enormous Kubernetes cluster<\/span>\u00a0<\/span>with a bunch of applications on it.<\/span>\u00a0<\/span>And other companies create Kubernetes clusters<\/span>\u00a0<\/span>for different workloads. B<\/span>oth believe that they\u2019re doing it properly.<\/span>\u00a0<\/span><\/p>\n

The second trend is<\/em> security related.<\/span>\u00a0<\/span>Every organization is struggling with the access silos,<\/span>\u00a0dreaming about a day<\/span>\u00a0<\/span>where they have one place,<\/span>\u00a0<\/span>with great user experience,<\/span>\u00a0<\/span>that simply spells out, \u2018this is what policy is<\/span>\u00a0<\/span>to access this particular data,\u2019<\/span>\u00a0<\/span>and it gets automatically enforced.<\/span>\u00a0B<\/span>ut every single cloud provider,<\/span>\u00a0<\/span>but every single application, but every single protocol,<\/span>\u00a0<\/span>but every single resource \u2014<\/span>\u00a0we don\u2019t have that unfortunately.<\/span>\u00a0<\/span>Teleport is slowly becoming that.<\/span><\/p>\n

Here\u2019s the complete video interview, part of SiliconANGLE\u2019s and theCUBE\u2019s coverage of <\/span>AWS re:Invent<\/span><\/a>:<\/span><\/p>\n