<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Scytale.io - Medium]]></title>
        <description><![CDATA[A blog dedicated to discussing the challenges of authenticating services in large-scale distributed software systems. - Medium]]></description>
        <link>https://medium.com/scytale-io?source=rss----5d7ecb3116f8---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Scytale.io - Medium</title>
            <link>https://medium.com/scytale-io?source=rss----5d7ecb3116f8---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:48:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/scytale-io" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[SPIFFE and SPIRE at KubeCon + CloudNativeCon Europe 2019]]></title>
            <link>https://medium.com/scytale-io/spiffe-and-spire-at-kubecon-cloudnativecon-europe-2019-f7debe9d706e?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/f7debe9d706e</guid>
            <category><![CDATA[istio]]></category>
            <category><![CDATA[spiffe]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[kubecon]]></category>
            <dc:creator><![CDATA[Umair M. Khan]]></dc:creator>
            <pubDate>Fri, 17 May 2019 15:42:39 GMT</pubDate>
            <atom:updated>2019-05-17T15:43:43.776Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>SPIFFE and SPIRE at KubeCon + CloudNativeCon Europe 2019</strong></p><p><em>Inspired by production infrastructure at Facebook, Google, Netflix and others the SPIFFE and SPIRE projects define a new standard for workload identity and authentication for cloud- and container-deployed microservices.</em></p><p>Kubecon EU 2019 is our biggest KubeCon yet! Less than two years after we launched the SPIFFE and SPIRE projects at KubeCon NA 2017 in Austin we have six fantastic talks covering all aspects of the project.</p><p>Speakers from <strong>Google</strong>, <strong>Tigera</strong>, and <strong>Scytale</strong> are covering open source best practices and integrations with projects like <strong>Envoy</strong>, <strong>Istio</strong>, <strong>Calico</strong> and <strong>Kubernetes</strong>, and security engineers from <strong>Uber</strong> giving a detailed case study of how they are using SPIRE in production.</p><p>If you’re building your schedule, here are the talks not to miss!</p><p><strong>Key SPIFFE and SPIRE Sessions:</strong></p><p><strong><em>Tuesday, May 21</em></strong></p><p><a href="https://kccnceu19.sched.com/event/MPib">Intro: SPIFFE</a><strong> </strong>(11:55am–12:30pm)<br><em>Emiliano Bernbaum &amp; Scott Emmons (Scytale)</em></p><p>New to SPIFFE/SPIRE? This session provides an introduction to the projects and the progress made over the past few months.</p><p><a href="https://kccnceu19.sched.com/event/MPfJ">Istio New Workload Identity Provision Pipeline Based on Envoy SDS</a> (11:55am–12:30pm)<br><em>Quanjie Lin &amp; Diem Vu (Google)</em></p><p>See how Istio’s new workload identity provision system leverages SPIFFE.</p><p><strong><em>Wednesday, May 22</em></strong></p><p><a href="https://kccnceu19.sched.com/event/MPe3">Zero Trust Service Mesh with Calico, SPIRE, and Envoy</a> (11:05am–11:40am)<br><em>Shaun Crampton (Tigera) &amp; Evan Gilman (Scytale)</em></p><p>Explore how to build a truly secure zero-trust service mesh with Layer 4 through 7 network policy enforcement using SPIRE and Calico.</p><p><a href="https://kccnceu19.sched.com/event/MPib">Deep Dive: SPIFFE</a><strong> </strong>(2:50pm–3:25pm)<br><em>Emiliano Bernbaum &amp; Scott Emmons (Scytale)</em></p><p>Learn best practices, suggestions, and recommendations on deploying and configuring SPIRE including in Kubernetes. For more details <a href="https://kccnceu19.sched.com/event/MPib">click here</a></p><p><strong><em>Thursday, May 23</em></strong></p><p><a href="https://kccnceu19.sched.com/event/MPdr">Securing Multi-Cloud Cross-Cluster Communication with SPIFFE and SPIRE</a> (2:00pm–2:35pm)<br><em>Evan Gilman (Scytale)</em></p><p>Learn how to leverage SPIRE to automate the issuance of SPIFFE identity across disparate orchestrators and platforms, allowing for seamless authentication of systems within and between them.</p><p><a href="https://kccnceu19.sched.com/event/MPe6">Uber x Security: Why and How We Built Our Workload Identity Platform</a> (4:45pm–5:20pm)<br><em>Tyler Julian (Uber) &amp; Daniel Feldman (Scytale)</em></p><p>Explore what led Uber to build out an automated, API-driven, cloud native approach to workload identity with SPIRE.</p><p><strong>Want to meet SPIFFE experts in person? Reach out to Evan (</strong><a href="https://twitter.com/evan2645"><strong>@evan2645</strong></a><strong>), Dan (</strong><a href="https://twitter.com/d_feldman"><strong>@d_feldman</strong></a><strong>) or Andres (</strong><a href="https://twitter.com/invariantly"><strong>@invariantly</strong></a><strong>), and find us on </strong><a href="https://slack.spiffe.io/"><strong>https://slack.spiffe.io/.</strong></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JgoRv0Xc5LIQdypX2Tjwsw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7debe9d706e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/spiffe-and-spire-at-kubecon-cloudnativecon-europe-2019-f7debe9d706e">SPIFFE and SPIRE at KubeCon + CloudNativeCon Europe 2019</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SPIFFE Community Day May 2019: Recap and Videos]]></title>
            <link>https://medium.com/scytale-io/spiffe-community-day-may-2019-recap-and-videos-61a672e0c728?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/61a672e0c728</guid>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cncf]]></category>
            <category><![CDATA[spiffe]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Umair M. Khan]]></dc:creator>
            <pubDate>Wed, 08 May 2019 16:36:36 GMT</pubDate>
            <atom:updated>2019-05-08T16:36:35.764Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AGc_Eu287VWdrk9b-fWv8g.png" /></figure><p><strong>SPIFFE Community Day May 2019: Recap and Videos</strong></p><p>Over the past few months, we’ve watched the SPIFFE and SPIRE projects grow in popularity and maturity as more and more organizations look at these projects to deliver service identity for cloud- and container-deployed services. The SPIFFE slack channel has gained over 100 new members since the last community day in November. <a href="https://spire.devstats.cncf.io/d/3/stars-and-forks-by-repository?orgId=1">By many measures</a> from the number of public forks to contributors, the project has roughly doubled in the last 12 months.</p><p>Last Friday Pinterest and Scytale hosted the May 2019 SPIFFE Community Day. In addition to project updates, this event featured fantastic demos and case studies from Uber, Square, Tigera and Scytale. Full event recording is<a href="https://www.youtube.com/watch?v=H5IlmYmEDKk&amp;feature=youtu.be"> posted here</a>.</p><p>Key sessions are listed below:</p><p>Latest <a href="https://youtu.be/H5IlmYmEDKk?t=1541"><strong>Project Updates</strong></a><strong> </strong>(SPIFFE + SPIRE)</p><p><strong>End User Talks:</strong></p><ul><li><a href="https://youtu.be/H5IlmYmEDKk?t=2585"><strong>SPIRE @ Square:</strong></a> Matthew McPherrin talked about how Square is using SPIFFE and SPIRE to ensure secure communications across hybrid infrastructure services.</li><li><a href="https://youtu.be/H5IlmYmEDKk?t=4703"><strong>SPIRE Scheduler Integration @Uber</strong>:</a> Tyler Dixon talked about his work of integrating SPIRE with workload schedulers and lessons learned along the way.</li></ul><p><strong>Demos:</strong></p><ul><li>Scott Emmons (Scytale) gives a detailed look at the new security model for <a href="https://youtu.be/H5IlmYmEDKk?t=6812"><strong>SPIRE on Kubernetes</strong></a>.</li><li><a href="https://youtu.be/H5IlmYmEDKk?t=7812"><strong>Transparent Service Authentication and Authorization With Calico, Envoy and SPIRE</strong></a><strong> </strong>This demo from Spike Curtis (Tigera) shows how Calico, Envoy and SPIRE can be used to deliver unified Layer 4 and Layer 7 authorization policies.</li><li><a href="https://youtu.be/H5IlmYmEDKk?t=8896"><strong>Securely extending the Istio Service Mesh into new environments with SPIRE</strong></a> This demo from Eugene Wiess and Max Lambrecht (Scytale) shows how services running outside of a Kubernetes cluster can securely authenticate to those running in an Istio service mesh on-cluster using SPIRE.</li></ul><p><a href="https://slack.spiffe.io/">Join us on Slack</a> to share ideas, ask questions, and learn from those using SPIFFE and SPIRE to implement zero-trust security.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61a672e0c728" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/spiffe-community-day-may-2019-recap-and-videos-61a672e0c728">SPIFFE Community Day May 2019: Recap and Videos</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SPIFFE Community Day May 3rd: Overview and Agenda.]]></title>
            <link>https://medium.com/scytale-io/spiffe-community-day-may-3rd-overview-and-agenda-994d7fc43b84?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/994d7fc43b84</guid>
            <category><![CDATA[spiffe]]></category>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[cloud-native]]></category>
            <dc:creator><![CDATA[Umair M. Khan]]></dc:creator>
            <pubDate>Tue, 23 Apr 2019 13:24:21 GMT</pubDate>
            <atom:updated>2019-04-29T19:48:55.275Z</atom:updated>
            <content:encoded><![CDATA[<p>The <a href="http://spiffe.io/">SPIFFE</a> project continues to grow in popularity and is catalyzing a standard, tooling, and ecosystem around service identity. Join us for the next SPIFFE community day on May 3rd.</p><p>This community day we have some fantastic demos and case studies. The event, hosted by <a href="https://www.pinterest.com/">Pinterest</a> and <a href="https://www.scytale.io/">Scytale</a>, will feature talks from Uber and Square engineers talking about how and why they have implemented SPIRE. Members of the community will also show hands-on demos of SPIRE on Kubernetes and integrations of SPIRE with the Istio, Calico, and Envoy projects.</p><p>If you are attending in person, the event will also provide an opportunity to catch up with your peers and the SPIFFE and SPIRE project maintainers.</p><p><a href="https://docs.google.com/forms/d/e/1FAIpQLSfkgzBB7OzfiR6igCMfdG1kYug6tikVRprmXpbjID4bNXo-iw/viewform"><strong>Sign up</strong></a> now if you have not already. Here are more details:</p><h3>Where is it?</h3><p>We are hosting the SPIFFE Community Day in <strong>San Francisco @ Pinterest </strong>(<a href="https://www.google.com/maps/place/Pinterest/@37.7775897,-122.3967268,15z/data=!4m2!3m1!1s0x0:0x4c729180cce69e0b?sa=X&amp;ved=2ahUKEwi6zZq2rrThAhWHdd8KHZYeD-8Q_BIwD3oECAoQCA">Google Maps</a>)</p><ul><li><a href="http://go.scytale.io/spiffe-may3"><strong>Register ASAP</strong></a><strong>.</strong> Seating capacity is limited, so register early!</li><li>Arrive at the Pinterest building lobby (with your ID) no later than 09:00 am PDT to accommodate sufficient check-in time.</li></ul><h3>When is it?</h3><ul><li>09:30 am — 1:00 pm PDT on Friday, May 3rd, 2019.</li></ul><h3>Attending via web</h3><p>We are using Google Meet for folks who want to participate solely via the web. As the event nears, registered participants can find the Google Meet link within the Google Calendar invite they will receive.</p><p>Join #community-day on Slack. We will use the SPIFFE Slack channel <strong>#community-day</strong> to facilitate discussions and communication. Go <a href="https://github.com/spiffe/spiffe#communications">here</a> to learn how to join SPIFFE’s Slack channel.</p><h3>Agenda (Work-in-Progress)</h3><p><strong>Early bird coffee &amp; networking — 9:00 am PT</strong></p><p><strong>Agenda: (Official Start @ 9:30am PT / 12:30pm ET)</strong></p><ul><li><strong>09:30–9:45: Opening Remarks &amp; Community “one-sliders”</strong></li><li><strong>09:45–10:00: SPIFFE Vision &amp; Roadmap</strong></li><li><strong>10:00–10:30: </strong>Project Updates (SPIFFE + SPIRE: What’s new?</li><li><strong>10:30–10:40: Break</strong></li><li><strong>10:40–11:25: End User Talks:</strong> Deploying SPIFFE and SPIRE</li></ul><p>— Tyler Dixon: SPIRE Scheduler Integration @ Uber</p><p>— Matthew McPherrin: SPIRE @ Square</p><ul><li><strong>11:25–11:35: </strong>Leveraging SPIFFE to bring Service and User Identity together — Nathanael Coffing</li><li><strong>11:35 -12:30: </strong>Demos + Q&amp;A</li></ul><p>— Running SPIRE on Kubernetes</p><p>— Transparent Service Authentication and Authorization With Calico, Envoy and SPIRE</p><p>— Integrating Istio and SPIRE</p><p>— And more!</p><ul><li><strong>Lunch/Networking @ 12:30 pm PT</strong></li></ul><h3>Food &amp; Beverage</h3><p><strong>SAN FRANCISCO</strong>: For those of you joining from San Francisco, Scytale will be providing lunch and coffee/tea for our participants!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rnACGAppI-N4JmMMKPlfWQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=994d7fc43b84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/spiffe-community-day-may-3rd-overview-and-agenda-994d7fc43b84">SPIFFE Community Day May 3rd: Overview and Agenda.</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello, Scytale Enterprise!]]></title>
            <link>https://medium.com/scytale-io/hello-scytale-enterprise-8c7fdc7906f?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/8c7fdc7906f</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[hybrid-cloud]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[Scytale Team]]></dc:creator>
            <pubDate>Mon, 04 Mar 2019 21:12:41 GMT</pubDate>
            <atom:updated>2019-03-04T21:12:41.316Z</atom:updated>
            <content:encoded><![CDATA[<p><em>tl;dr Scytale today launched Scytale Enterprise, the industry’s first cloud-based subscription offering that enables enterprises to use policies to authenticate cloud-based services with on-premise infrastructure in a compliant manner.</em></p><p>In 2016, I began meeting with Fortune 500 security leaders in Boston, Chicago, New York, San Francisco, and Washington DC, and asked them one simple question that while seemingly straightforward produced some pretty complicated answers:</p><blockquote><strong>“How will you authenticate your cloud services with your on-premise infrastructure?</strong></blockquote><p>Modern software services are more interconnected and interdependent than ever before. Moreover, as organizations begin moving these services to increasingly dynamic cloud computing platforms (think VMs, containers, serverless, functions, etc.), their services must also become more dynamic.</p><p>As organizations adopted these platforms because of the promise of increased business velocity, their authentication strategies needed to evolve, too. What many now have is a complex web of legacy identity and access management (IAM) investments and platform-specific identity providers (IdPs), coupled with costly “glue code” to support their hybrid cloud evolution. This slowed application security reviews, increased costs, and increased time-to-market for new applications.</p><p>Many would say that while compliant with existing authentication control requirements, they felt some of their bad on-premise authentication “habits” were finding their way into their cloud investments. For example, many were uncomfortable with using the same legitimately provisioned credentials across multiple cloud services … mostly for the sake of convenience. As this group observed hybrid cloud and multi-cloud aggressively coming towards them, it became clear to them that their service authentication strategy needed to evolve, too.</p><p>In 2017, we helped our community launch <a href="https://www.spiffe.io/"><strong>SPIFFE</strong></a> and SPIRE to give enterprise IT security engineers a more scalable, cloud-native primitive to help them more efficiently and consistently authenticate their cloud-based infrastructure. We’ve since seen uptake and early adoption from organizations like Google, Pinterest, Square, Uber, and more, as well as interest from a growing number of other OSS projects.</p><p>The aforementioned security leaders said that while SPIFFE and SPIRE are an important step in the correct direction, any new identity framework MUST co-exist with the considerable investments they had with other IdPs like Microsoft Active Directory and more. In fact, what they really wanted was a scalable, platform-agnostic way of <em>extending</em> Active Directory’s reach to their cloud-based services, even those running in Microsoft Azure. Whatever the solution, they all made two things very clear to me: 1) do not compromise their existing security posture; and 2) do not worsen their developers’ cloud deployment experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SCZQqB9ffruHW6s2Ar2Eqw.jpeg" /></figure><p><strong>Introducing Scytale Enterprise</strong></p><p>On behalf of our amazing <em>Scyphers</em> (what we call ourselves), I’m delighted to introduce <a href="https://www.scytale.io/enterprise"><strong>Scytale Enterprise</strong></a>, which helps enterprises extend their existing service-based IAM and authentication investments to the cloud. It runs in the cloud and on-premise and can be purchased as an annual subscription offering.</p><p>Scytale Enterprise delivers to enterprises a flexible solution to authenticate services regardless of which platform they run upon or the myriad of requisite identities used by current authentication controls. Using SPIFFE and SPIRE as our foundation, Scytale Enterprise supports authentication for elastically-scaled and ephemeral cloud-native services. It also supports enterprise identity providers like Microsoft Active Directory and AWS Identity and Access Management (IAM), authentication protocols like Kerberos and oAuth, and popular authentication clients, too.</p><p>Scytale Enterprise also allows organizations to solve for the emerging challenge of <a href="https://www.csoonline.com/article/3247848/what-is-zero-trust-a-model-for-more-effective-security.html"><strong>Zero Trust</strong></a> — enforcing robust, application-centric security controls — by delivering strongly attested, frequently rotated cryptographic identities to any service.</p><p>We designed Scytale Enterprise’s initial feature set in collaboration with several Fortune 100s who found their way to us through SPIFFE. Some important aspects of the offering include the following:</p><ul><li><strong>Platform-agnostic service identity</strong>: Separate identities from infrastructure to securely and scalably connect services across heterogeneous platforms.</li><li><strong>Designed for dynamic environments</strong>: Easily manage identity in today’s cloud and containerized environments.</li><li><strong>Policy-driven service lifecycle management</strong>: Automates steps such as identity issuance, attestation, and certificate rotation according to multi-factor policies.</li><li><strong>Centralized service directory</strong>: Delivers a centralized directory for all service identities alongside any on-premise IdPs.</li><li><strong>Based on an open-source standard (SPIFFE):</strong> Built on a standard designed by industry leaders, ensuring flexibility and security.</li></ul><p>To learn more, <a href="https://scytale.io/enterprise"><strong>schedule a demo</strong></a> with us. We’d love to learn more about how we can help you accelerate your cloud and container migration efforts.</p><p>Also, if you are attending RSA Conference 2019 this week in San Francisco, stop by startup booth 103 and/or <a href="http://eventbrite.com/e/spiffe-networking-rsa-conference-2019-tickets-56455915162"><strong>attend our Monday evening mixer</strong></a><strong>!</strong> And whether you’re in town or not, follow us at <a href="http://scytale_io/"><strong>@scytale_io</strong></a> to learn where we’re going next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c7fdc7906f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/hello-scytale-enterprise-8c7fdc7906f">Hello, Scytale Enterprise!</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Cloud and Containers Require a New Approach to Service Authentication]]></title>
            <link>https://medium.com/scytale-io/why-cloud-and-containers-require-a-new-approach-to-service-authentication-c41c4769e1f8?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/c41c4769e1f8</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[zero-trust]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[spiffe]]></category>
            <dc:creator><![CDATA[Andrew Jessup]]></dc:creator>
            <pubDate>Wed, 27 Feb 2019 20:08:11 GMT</pubDate>
            <atom:updated>2019-02-28T21:58:26.836Z</atom:updated>
            <content:encoded><![CDATA[<p>20 years ago, “service authentication” was a relatively simple proposition for enterprise security teams. First, enterprises typically only had a few services to manage within their own datacenters. Second, these services usually executed on a relatively small and stable set of interconnected physical machines.</p><p>Modern enterprise software architectures are nowhere as simple. Customer-facing services rely upon a myriad of interdependent internal software services that are managed by different teams in different lines of business, and running on widely divergent technology stacks.</p><p>Not only has there been a recent explosion in the number of services, but the environments in which these services operate are more complex than ever before. Technologies like cloud computing allow faster releases of more resource-efficient applications and services, but they have also forced enterprises to evolve towards more complex security models to protect existing on-premise services and new cloud-based services.</p><p>Containers and functions add complexity to this already challenging landscape. Services are now not only elastically scaled but also dynamically scheduled and ephemeral — moving from machine to machine at a moment’s notice. Static network identifiers like IPv4 or IPv6 addresses are largely meaningless in this world from an authentication perspective — requiring once again a shift in how services built on these technologies can be secured alongside existing systems.</p><p>The confluence of these trends — microservices, cloud, and containers — creates substantial new challenges for security teams. Network perimeters, established by firewall rules, are insufficiently dynamic to be able to isolate and protect inter-service communication in such a heterogeneous environment.</p><p>In many cases, even coarse-grained network protection is insufficient as enterprises seek to mix highly trusted services (such as PCI-certified payment systems) on the same platforms as less trusted systems (such as those developed by contractors). It is increasingly becoming necessary to assume that even the internal network is, to some extent, hostile.</p><p>For organisations seeking to rely less on the network — they must instead rely on services themselves to establish trust between each other — and to be able to encrypt traffic between each other. This is the premise of “zero trust” networking. And zero trust networking relies on strong authentication between services core to establish trust.</p><p><strong>Re-thinking service authentication for a zero-trust world</strong></p><p>While identity and authentication standards — such as Kerberos and oAuth — do exist today and are widely employed, they are generally unsuitable as the foundation of a scalable zero-trust network. In 2017 we recognized that for a service identity framework to supporting zero-trust it would need to embody 10 key characteristics:</p><ol><li><strong>Support both identity and confidentiality. </strong>Users should be able to use the system to guarantee both identity of a service as well as and the integrity and privacy of communication to it. Modern proven cryptographic systems should be leveraged to verify the identity of both source and destination.</li><li><strong>Be cloud- and container- friendly</strong>. The framework should work well in elastically scaled cloud environments, and dynamically orchestrated containerized environments, as well as environments that are neither.</li><li><strong>Be easy to use</strong>. Installing or correctly using the framework shouldn’t require deep knowledge of topics like cryptography or public key infrastructure. It should be possible to use the framework to secure existing systems with little or no code change.</li><li><strong>Support “multi-factor” identity</strong>. Instead of using hard-to-secure techniques like an API key or username and password, trusted third parties like orchestrators, CI/CD pipelines, cloud platform control planes, and secure enclaves should be used in concert to establish the identity of a service uniquely in any environment. This has an advantage too that a service does not need to be made aware of its own identity is before it is deployed.</li><li><strong>Be reliable at scale</strong>. To be reliable at scale — particularly for cloud-hosted services — any identity must be able to operate smoothly even when parts of the system are subject to a failure. Two services should be able to authenticate successfully even if other supporting services (such as a centralized identity server) are temporarily unavailable.</li><li><strong>Work across varying authentication use-cases</strong>. While often authentication is thought of in the context of authenticating an HTTP API call, “authentication” also applies to many other use-cases such as securing a TCP stream, or signing a message on a queue. An identity framework should support these use-cases.</li><li><strong>Separate the concerns of development and operations teams</strong>. Delivery of a service into production (including configuring how that application authenticates to another) requires deep cooperation between the development teams that build the software and the operations teams that are responsible for securing, deploying and maintaining those services. By standardising on an API between a service and its operating environment for authentication, this cooperation can be greatly simplified.</li><li><strong>Quarantine privileged knowledge. </strong>A compromised machine should never ever compromise any secrets for services running elsewhere.</li><li><strong>Be federate-able</strong>. It should be possible to use identities to establish trust across and between enterprises or business units that don’t share common IT systems.</li><li><strong>Be fully autonomous</strong>. In an enterprise IT environment that’s both ephemeral and dynamic, establishing trust must be policy-driven, automated, and audit-able.</li></ol><p><strong>SPIFFE and SPIRE, the open-source foundation for service identity</strong></p><p>Inspired by these principles, as well as building on the established patterns from organisations such as Google, Facebook, and Netflix, Scytale and others together developed the open-source <a href="https://spiffe.io/">SPIRE project and SPIFFE standard</a>. These projects, now under the auspices of the Cloud Native Computing Foundation (CNCF), allow organisations of all stripes to easily implement best practices for service authentication in a wide range of operating environments.</p><p>Specifically, the projects’ goals are to ensure that any service, running anywhere, can retrieve a short-lived, cryptographically verifiable identity, either as a JWT bearer token or as an X.509 key and certificate.</p><p>We’ve been thrilled with the interest and growing gravity around these projects since their 2017 launch. In 2019 alone, we’ve seen significant project contributions from <a href="https://github.com/spiffe/spire/pull/751">Square</a>, <a href="https://github.com/spiffe/spire/pull/687">Uber</a>, and <a href="https://spire.devstats.cncf.io/d/5/companies-summary?orgId=1">several others</a>.</p><p>Just as importantly, we’ve begun seeing a growing community of open-source projects align around SPIFFE. Integrations now exist for <a href="https://blog.envoyproxy.io/using-spire-to-automatically-deliver-tls-certificates-to-envoy-for-stronger-authentication-be5606ac9c75">Envoy</a>, <a href="https://blog.scytale.io/unifying-observability-with-spiffe-77ef9413ae66">OpenTracing</a>, <a href="https://blog.scytale.io/nginx-spire-a63ce46d9a5">nginx</a>, <a href="https://istio.io/docs/concepts/security/">Istio</a>, <a href="https://medium.com/@Pinterest_Engineering/secret-management-in-multi-tenant-environments-debc9236a744">Knox</a>, and <a href="https://github.com/square/ghostunnel">Ghostunnel</a>, with more on the way.</p><p>As SPIFFE and SPIRE continue to grow and evolve under the auspices of the CNCF and a growing set of contributors, Scytale continues to serve as a key contributor and steward of the projects.</p><p><strong>RSA 2019: bringing service identity management to the cloud-native enterprise</strong></p><p>Scytale’s work doesn’t stop with SPIFFE. Since 2017, we’ve engaged with 100+ enterprises (including several Fortune 100s) about their emerging challenges for service authentication as multi-cloud and containers become an inevitable part of their IT roadmap.</p><p>These organisations recognize the enormous opportunity to use SPIFFE and SPIRE to standardize their identity model across multiple cloud, container, and on-premise deployments. But, they also emphasized the importance of reconciling this with existing (and mission-critical) investments in identity and entitlements.</p><p>We’ve been hard at work solving these challenges and are showing a sneak peek next week of our commercial offering at the RSA conference in San Francisco. If you’re attending the conference, stop by startup booth 103 or <a href="http://eventbrite.com/e/spiffe-networking-rsa-conference-2019-tickets-56455915162">join us at our mixer on Monday night</a> to learn more and meet us! And whether you’re in town or not, follow us at <a href="http://scytale_io/">@scytale_io</a> to learn where we’re going next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c41c4769e1f8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/why-cloud-and-containers-require-a-new-approach-to-service-authentication-c41c4769e1f8">Why Cloud and Containers Require a New Approach to Service Authentication</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Scytale Essentials & Scytale Professional Services]]></title>
            <link>https://medium.com/scytale-io/spiffe-subscription-aa020c975c8d?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/aa020c975c8d</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[professional-services]]></category>
            <category><![CDATA[spiffe]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[api-security]]></category>
            <dc:creator><![CDATA[Andrew Jessup]]></dc:creator>
            <pubDate>Tue, 12 Feb 2019 12:51:00 GMT</pubDate>
            <atom:updated>2019-02-12T12:51:00.804Z</atom:updated>
            <content:encoded><![CDATA[<p><strong><em>tl;dr as SPIFFE grows, Scytale is today introducing two commercial offerings to help organizations accelerate and optimize their deployments.</em></strong></p><p>It has been a remarkable fourteen months since we and the broader community launched SPIFFE at <a href="https://www.youtube.com/watch?v=ikmxZdZRTio">KubeCon North America 2017</a>. Our collective intention for this project was to address a fundamental enterprise security problem: how to get two services within a distributed infrastructure to reliably trust each other … without hard-coded credentials.</p><p><strong>Why SPIFFE?</strong></p><p>SPIFFE was inspired in part by our experiences working at Internet-scale businesses like Amazon Web Services, Google, and Netflix. We saw first-hand how their novel approaches to service identity allowed these organizations to successfully tame the complexity that comes with securing and deploying thousands of microservices built by varying engineers into complex, dynamic, and heterogeneous IT environments.</p><p>Yesterday, the challenge of maintaining an iron-clad security posture in the face of large numbers of services, independent software teams, elastic scaling, and heterogeneous hosting environments was largely the domain of Internet-scale organizations experiencing explosive growth. Today, with the rise of microservices, multi-cloud, containers, serverless, and continuous integration, many Fortune 1000 IT security engineers are feeling these same headwinds. Faced with new complexity and threat models, they seek solutions from those who have gone before. We knew the time was right for a service authentication technology like SPIFFE.</p><p><strong>SPIFFE accelerates in 2018</strong></p><p>Since December of 2017, we’ve been astounded by the community response to what should have been an esoteric security tool. In barely one year, we’ve seen contributions from Square, Tigera, Heptio, Uber, and VMWare. SPIFFE has found its way into several <a href="https://blog.envoyproxy.io/securing-the-service-mesh-with-spire-0-3-abb45cd79810">popular</a> open-source <a href="https://github.com/square/ghostunnel">proxies</a>, <a href="https://medium.com/@Pinterest_Engineering/secret-management-in-multi-tenant-environments-debc9236a744">secret stores</a>, <a href="https://www.consul.io/segmentation.html">service discovery tools</a>, and <a href="https://istio.io/blog/2017/0.1-auth/">service meshes</a>.</p><p>The <a href="https://spiffe.io/spire/">SPIRE project</a> — SPIFFE’s leading implementation — has also evolved, with support on three major public cloud platforms, container orchestration technologies like Kubernetes, and various on-premise technologies. Its extensible architecture enables interoperability with third-party datastores, hardware security modules, certificate authorities, and ITSM tooling.</p><p>In March 2018, SPIFFE and SPIRE were <a href="https://github.com/cncf/toc/pull/68">voted into the Cloud Native Computing Foundation</a>, the same independent foundation that supports the Kubernetes and Prometheus open-source projects.</p><p>More than 1,800 commits later, SPIFFE and SPIRE are taking hold and growing, as more and more organizations are beginning to regard it as a foundational component of their next-generation multi-cloud security strategy.</p><p><strong>Introducing Scytale Essentials and Scytale Professional Services</strong></p><p>As a leading contributor to SPIFFE and SPIRE, Scytale recognizes a successful deployment of these technologies requires careful planning and execution. Today, we’re excited to announce unprecedented access to our own expert engineers and our experience gained from advising many organizations. We will be delivering this through two commercial offerings: <strong><em>Scytale Essentials</em></strong> and <strong><em>Scytale Professional Services</em></strong>.</p><p><strong>Scytale Essentials</strong> gives organizations implementing SPIFFE and SPIRE the comfort and security of working with a supportive and experienced partner, while also maintaining the benefits of vendor-neutral open-source software. This subscription includes access to a Scytale-supported, production-hardened distribution of SPIRE that closely tracks the CNCF release, but also includes immediate access to critical bug fixes and security patches. The subscription also includes a service-level agreement for bug fixes and inquiries, root cause analysis, office hours, and a dedicated technical account manager.</p><p><strong>Scytale Professional Services </strong>complements Scytale Essentials with on-demand access to dedicated expertise when planning, deploying, and scaling SPIRE, as well as complementing an organization’s existing engineering team with engineering resources as needed.</p><p>If you are on the path to evaluate, plan, implement, and/or scale SPIFFE and SPIRE, visit <a href="https://www.scytale.io/spiffe">https://www.scytale.io/spiffe</a> to learn more about these programs and schedule a consultation with us.</p><p>We’re looking forward to speaking with you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa020c975c8d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/spiffe-subscription-aa020c975c8d">Introducing Scytale Essentials &amp; Scytale Professional Services</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recapping SPIFFE Community Day Q418]]></title>
            <link>https://medium.com/scytale-io/what-was-new-at-spiffe-november-community-day-5a3a7e995eb5?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/5a3a7e995eb5</guid>
            <category><![CDATA[spiffe]]></category>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[jwt]]></category>
            <category><![CDATA[api]]></category>
            <category><![CDATA[community-day]]></category>
            <dc:creator><![CDATA[Umair M. Khan]]></dc:creator>
            <pubDate>Thu, 10 Jan 2019 18:55:06 GMT</pubDate>
            <atom:updated>2019-01-11T01:39:11.473Z</atom:updated>
            <content:encoded><![CDATA[<p>Scytale hosted SPIFFE’s seventh community day in November 2018. This event was a great way for participants to learn the latest SPIFFE/SPIRE updates, and to meet peers and practitioners. Being new to this community, it was a great learning experience for me. It certainly felt like drinking from a firehose!</p><p>The event nearly doubled in attendance, with 150+ participants representing various industries attending in person in San Francisco and New York and online.</p><p>The <a href="http://go.scytale.io/spiffe-community-day-2018-nov-agenda">agenda</a> was full of project updates, demos, and user presentations from organizations including Pinterest, Square, and VMware. Of the many project updates, two stood out for me:</p><ul><li><strong>SPIFFE Federation</strong>: In today’s enterprise, a natural tension exists between a desire for a contiguous service identity namespace with consistently applied and auditable policies, and a desire for isolation and autonomy. Some examples of this include when distinct business units are supported by independent platforms teams but must establish mutual trust. The SPIFFE community foresees that adopters will want to establish mutual trust between SPIFFE-compatible vendors.</li><li><em>SPIFFE Federation</em> is a proposal to build trust between two identity namespaces, running across heterogeneous platforms. Work is being done in SPIFFE to define a standard interface for federation support, and in SPIRE to implement that interface. <a href="https://www.youtube.com/watch?v=8VE8TKCuS_I&amp;feature=youtu.be&amp;t=485">Here’s Scytale’s Max Lambrecht</a> discussing the upcoming Federation API.</li><li><strong>JWT Support:</strong> Many organizations want to use JWT-based tokens for service-to-service authentication, but up till now the only way to authenticate using a SPIFFE ID was via an X.509 certificate. While this suffices for many use-cases (eg. mTLS), there are others where mTLS is unsuitable (e.g. when an application load balancer is in the network path, or when queue messages must be identified). A group of SPIFFE contributors has been working on a JWT-based token specification of the SPIFFE ID (the JWT-SVID), and a mechanism to generate and validate these tokens via the SPIFFE Workload API. This <strong>GREATLY</strong> simplifies JWT-based authentication between workloads. <a href="https://www.youtube.com/watch?v=8VE8TKCuS_I&amp;feature=youtu.be&amp;t=1415">Here’s Scytale’s Andrew Harding</a> discussing the JWT support.</li></ul><p>Interested in learning more? P<a href="https://www.youtube.com/watch?v=8VE8TKCuS_I">resentations</a> and <a href="https://www.youtube.com/watch?v=2rMSS8tDevM">demos</a> are now available on YouTube.</p><p>A big thank you to all presenters, contributors, and attendees for making it a huge success. Special thanks to Square (in San Francisco) and <a href="https://www.work-bench.com/">Work-Bench</a> (in New York) for hosting the SPIFFE community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/0*JnBn7irH9Xbushns" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a3a7e995eb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/what-was-new-at-spiffe-november-community-day-5a3a7e995eb5">Recapping SPIFFE Community Day Q418</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Square & Pinterest share their SPIFFE story on Community Day]]></title>
            <link>https://medium.com/scytale-io/square-pinterest-share-their-spiffe-story-on-community-day-26e2d04aac0d?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/26e2d04aac0d</guid>
            <category><![CDATA[spiffe]]></category>
            <category><![CDATA[square]]></category>
            <category><![CDATA[pinterest]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[identity-management]]></category>
            <dc:creator><![CDATA[Umair M. Khan]]></dc:creator>
            <pubDate>Thu, 10 Jan 2019 18:54:25 GMT</pubDate>
            <atom:updated>2019-01-10T18:54:25.649Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Square &amp; Pinterest talk about how they are using SPIFFE</strong></h3><p><a href="http://scytale.io/">Scytale</a> recently hosted <a href="http://spiffe.io/">SPIFFE’s</a> quarterly Community Day. The event is a great way to learn about the latest updates on SPIFFE/SPIRE and also hear from peers about their experience with the solutions.</p><p>This time around both Square and Pinterest shared problems they are solving with SPIFFE and SPIRE.</p><p><strong>Why SPIFFE &amp; SPIRE @ Square?</strong></p><p>At Square, product teams are given the flexibility to choose technology stacks that best fit their specific needs. As a result, Square began to deploy a number of heterogeneous hosting and middleware platforms running across their data centers and cloud. As a result, it became increasingly difficult for applications across different platforms to securely and easily trust and talk to each other using platform native identities.</p><p>Square wanted a service identity management mechanism that was not limited to a single platform. SPIFFE was attractive in that it provided them with an interoperable standard to ensure secure communication between services (even on different infrastructure providers and between containerized and non-containerized services). Another attractive property is that, due to the independent SPIFFE specification, they were not locked into a specific implementation.</p><p>They chose to explore SPIRE as it had support for cloud and Kubernetes built in, as well as being easy to customize for their own data centers and existing software toolchain.</p><p><a href="https://www.youtube.com/watch?v=2rMSS8tDevM&amp;feature=youtu.be&amp;t=3550">Watch Matt McPherrin talk about how SPIFFE is being deployed at Square</a> and their strategy for their datacenter and cloud (Kubernetes in AWS &amp; GCP) here.</p><p><strong>Why SPIFFE @ Pinterest?</strong></p><p>Jeremy Kratch from Pinterest talked about how they moved from doing ad-hoc authentication, (commonly done static tokens or network ACLs) to what he calls “SPIFFEology” (aka SPIFFE/Service-centric identities). The two biggest reasons for this move were:</p><ul><li><strong>Lack of support for Multi-tenant environments: </strong>As Pinterest started to deploy services into multi-tenant environments to meet scalability needs, using hostnames (provided by a network) as a form of identity didn’t cut it anymore as these hostnames are the same across tenants and not unique. It is also difficult to independently verify a source service’s hostname and thus it hostnames cannot be easily trusted. Finally, it is obviously a security advantage to encrypt traffic between workloads in multi-tenant environments.</li><li><strong>Increasing engineering complexity and slower time to market: </strong>Since various development teams began to use heterogeneous, dynamic platforms, using hostnames as a form of identity became time-consuming. They were spending a lot of effort in creating complex, error-prone regular expressions, to compensate for the varying patterns of hostnames across tools.</li></ul><p>SPIFFE allows them to easily provide an ID to each service which makes creating policy easy for services owners and eliminates the reliance on hostnames or the network.</p><p><a href="https://www.youtube.com/watch?v=2rMSS8tDevM&amp;feature=youtu.be&amp;t=3865">Watch Jeremy Kratch talk about how Pinterest is using SPIFFE</a></p><p>Are you looking to deploy SPIFFE or SPIRE into your production environment? Ping me (Umair Khan) on the <a href="https://slack.spiffe.io/">SPIFFE Slack channel</a> if you are interested in presenting at our next community day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/0*wgmq3KkBrf7d8MBG" /><figcaption>Image source: pexels.com</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26e2d04aac0d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/square-pinterest-share-their-spiffe-story-on-community-day-26e2d04aac0d">Square &amp; Pinterest share their SPIFFE story on Community Day</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Federating SPIFFE Domains]]></title>
            <link>https://medium.com/scytale-io/federating-spiffe-7d7db8040c3?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/7d7db8040c3</guid>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Daniel Feldman]]></dc:creator>
            <pubDate>Thu, 13 Dec 2018 14:58:14 GMT</pubDate>
            <atom:updated>2018-12-13T17:05:14.577Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZMKp5-kwvKDQoC295SI1Fg.jpeg" /><figcaption>Credit: <a href="https://www.pexels.com/photo/red-brown-wishing-locks-during-daytime-47063/">pexels.com</a></figcaption></figure><h3>Work-in-Progress: Federating SPIFFE Trust Domains</h3><h3>Introduction</h3><p>Federating trust domains is one of <a href="https://spiffe.io/">SPIFFE</a> and <a href="https://spiffe.io/spire">SPIRE</a>’s most requested, actively developed features. In this blog post, I will provide an overview of our current plan and the challenges in implementing it.</p><p><strong>What is federation?</strong></p><p>Certificates in a SPIFFE trust domain share a single root of trust. This is currently a root trust bundle consisting of several certificates that are shared between and within control planes using non-standardized formats and protocols.</p><p>This isn’t good enough, however. Many organizations have multiple roots of trust: perhaps because they have different organizational divisions with different administrators, or because they have separate staging and production environments that occasionally need to communicate. A similar use-case is SPIFFE interoperability between organizations, such as between a cloud provider and its customers. Both use-cases require a well-defined, interoperable method for a workload in one trust domain to authenticate a workload in a different trust domain. This is <em>federation</em>.</p><p><strong>Federation design</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*5rkQBr0zZuTGxrkGeX5Cfw.png" /></figure><p>To implement federation, we must share public keys between different SPIFFE servers. This isn’t a one-time operation; because of key rotation, each trust domain’s public key changes periodically. Each federating domain must download the other domain’s public keys periodically, at a frequency at least as fast as key rotation.</p><p>The data format for periodically downloading certificates isn’t finalized yet. Our current thinking is to have SPIFFE implementations use the <a href="https://tools.ietf.org/html/rfc7517">JWKS</a> format to publish certificates publicly at a well-known URL. Then, to start a federation relationship, implementations can download the JWKS data and import the certificates from it.</p><p>We like JWKS because it is a generic, extensible format for sharing key information that can accommodate JWT and X.509 certificates. (For security reasons, SPIFFE requires different key material for JWT and X.509 identities — they can’t just be the same public keys encoded in different formats.) JWKS’ flexibility allows a single federation API to support both JWT and X.509.</p><p><strong>Workload API</strong></p><p>The <a href="https://github.com/spiffe/spiffe/blob/master/standards/SPIFFE_Workload_API.md">SPIFFE workload API</a> provides endpoints for reading federated public keys. This API is distinct from the API for reading the certificates for the current trust domain, so applications can distinguish between clients from the local and federated domains.</p><p><strong>Experimental support in SPIRE</strong></p><p>Even though it is not officially standardized as part of SPIFFE yet, an experimental implementation of JWKS is already available in SPIRE.</p><h3>Challenges</h3><p><strong>Initial authentication of the foreign SPIFFE server</strong></p><p>There’s a bootstrapping problem with the federation API: if neither side shares a trust root, there’s no way to establish an initial secure connection. One solution is to use web PKI with a certificate authority that both SPIFFE servers trust. Another solution is to use manual authentication mechanisms to obviate the need for a public certificate authority (CA).</p><p>SPIRE implements federation similarly to node and workload registration. As we extend the registration API, it will be possible to manipulate federation through that API much like node and workload registration.</p><p><strong>Network outage tolerance</strong></p><p>Each time a SPIFFE implementation imports new certificates from a peer SPIFFE implementation, it authenticates the connection using the last known bundle. If there’s a long network outage and two SPIFFE implementations can’t communicate for more than a full key rotation cycle, then they won’t be able to communicate going forward, thus breaking the federation relationship.</p><p>One solution is to set the key rotation interval longer than the longest possible network outage length (or re-initialize federation if a long outage occurs). This is a design tradeoff: if the key rotation interval is longer, a compromised key will remain valid for a longer period as well.</p><p>Alternatively, if web PKI is available for the SPIFFE servers, that can be used to secure the federated connection. We believe web PKI between federated SPIFFE servers will be a common design pattern because it avoids the issue with long network outages breaking key rotation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*FpsXiSUtCtL5erfJH0cN9A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*6PmHddYM0eHUfMh6kBQYSw.png" /></figure><p><strong>Transitive &amp; two-way federation</strong></p><p>Kerberos and Active Directory have the equivalent of federation, called “cross-realm trust.” In most cases, cross-realm trust is <em>two-way </em>(both sides trust each other) and<em> transitive </em>(if A trusts B, and B trusts C, then A trusts C)<em>.</em></p><p>Two-way federation in SPIFFE is usually, but not always, desirable. For public APIs, the API provider may want to use web PKI to secure the server side of the connection, and SPIFFE to secure the client side. Because of this, we do not automatically configure two-way federation.</p><p>For large organizations with many trust domains, transitive federation may simplify implementation complexity. However, transitive federation can make it difficult to reason about the security properties of a SPIFFE implementation. For this reason, we are not implementing transitive federation in SPIFFE right now.</p><p>For now, users must manually configure transitive and two-way federation by adding more federation relationships.</p><p><strong>Scoping of federated trust domain SVIDs</strong></p><p>In web PKI, everyone trusts the same root certificate authorities. In SPIFFE, organizations that don’t entirely trust each other may still want to federate their trust domains. Applications must verify that each SVID is issued by a SPIFFE server that owns that trust domain.</p><p>Imagine a strange world where Coke and Pepsi must exchange data. To do this, they federate their respective trust domains. Coke’s SPIFFE certificate root is added to Pepsi’s trust store, and vice versa. In a simple implementation of certificate validation, a Coke server could fraudulently impersonate a Pepsi server on Pepsi’s network, since Pepsi trusts Coke’s root certificates!</p><p>Here’s the problem: root certificates aren’t “scoped.” Any CA can sign a certificate for any name. This is fine if all CAs are trusted, for example within a single company. In an environment with multiple CAs, each of which should only be allowed to sign certificates with specific names, it leads to security holes.</p><p>One approach to prevent this would be to use the X.509 <a href="https://tools.ietf.org/html/rfc5280#section-4.2.1.10">Name Constraints extension</a>. The Name Constraints extension allows a CA certificate to be limited to issuing certificates for a particular domain name. However, support for the Name Constraints extension is limited in TLS libraries, and it does not solve the problem for future SPIFFE identity formats such as JWT. For these reasons, SPIFFE is not including the Name Constraints extension.</p><p>This means all applications that use SVIDs must check that the SPIFFE ID in the SVID matches the trust domain of the actual CA that signed the certificate. That means checking that a Pepsi SVID isn’t signed by Coke’s CA. Current widely-used applications, such as web servers and proxies, don’t perform this check.</p><h3>Conclusion</h3><p>Federation is critical to implement for SPIFFE to be successful. However, there are challenges ahead to implement it in a secure and usable way. We’re working hard with the community to work our way through these challenges, and would love to hear from you if you have perspective!</p><p>To learn more about SPIFFE federation:</p><ul><li>Check out the new <a href="https://github.com/spiffe/spiffe-example/tree/master/java-spiffe-federation-jboss">Java SPIFFE Federation Demo</a>, which demonstrates working federation between two domains using SPIRE in a Tomcat server environment.</li><li>Join the<a href="http://spiffe.slack.com/"> SPIFFE Slack</a> to discuss SPIFFE with experts.</li><li>Join the <a href="https://github.com/spiffe/spiffe">SPIFFE SIG-SPEC</a> bimonthly meetings to design the future of federation in SPIFFE. (There will soon be a separate Federation Working Group.)</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d7db8040c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/federating-spiffe-7d7db8040c3">Federating SPIFFE Domains</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hello, Scytale!]]></title>
            <link>https://medium.com/scytale-io/hello-scytale-f35b94b28c67?source=rss----5d7ecb3116f8---4</link>
            <guid isPermaLink="false">https://medium.com/p/f35b94b28c67</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[identity]]></category>
            <category><![CDATA[identity-management]]></category>
            <category><![CDATA[startup-life]]></category>
            <dc:creator><![CDATA[ryan nelson]]></dc:creator>
            <pubDate>Mon, 26 Nov 2018 22:00:36 GMT</pubDate>
            <atom:updated>2018-11-26T22:00:35.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7bT7JYCfd7zKxxvpc0taw.jpeg" /><figcaption>Connecting all the things! (Image from <a href="http://fffff.at/free-universal-construction-kit/">http://fffff.at/free-universal-construction-kit/</a> )</figcaption></figure><p>Hi! I’m Ryan Nelson. I recently joined Scytale to help our user base tackle the sorts of problems that <a href="https://softwareengineeringdaily.com/2018/11/14/spiffe-zero-trust-workload-identification-with-evan-gilman/">zero-trust</a> architectures and <a href="https://spiffe.io/spiffe/">SPIFFE</a> address.</p><p>If you’re a potential customer, call me “Sales Engineering” or “Technical Evangelist.” If you’re already a customer or partner, call me “Field Engineering” — or just call me! ☺</p><p>Throughout my career, there’s been a common thread — I’m someone who:</p><ul><li>architects and connects systems to the internet, and to each other (I’m a computer nerd)</li><li>cares about the security of those systems (confidentiality, integrity, availability)</li><li>likes to chat with other people about it (I’m pretty social)</li></ul><p>I’ve noticed that when enterprises try to break apart their monolithic systems and distribute them into cloud-centric, dynamic, utility-compute environments, they run into some interesting problems. Breaking apart large, troublesome internet systems has been working for me for <a href="https://www.linkedin.com/in/ryancnelson/">quite a while now</a>. (The picture above is from plans for <a href="http://fffff.at/free-universal-construction-kit/">“connect this to that” parts</a> I 3D-printed for my son, when we needed to integrate some of his LEGO with a “legacy” Lincoln Logs system.)</p><p>I’m excited to join Scytale because I get to engage directly with lots of smart people solving those kinds of problems.</p><p>At <strong>Major League Baseball</strong> (and before that at a large international portal website), when burdened with sudden success, my co-workers and I tackled <a href="https://conferences.oreilly.com/velocity/velocity2009/public/schedule/detail/10207">traffic surges</a> by re-architecting with CDNs, <a href="https://memcached.org/">local-caches</a>, and SOA/microservices, <a href="https://www.networkworld.com/article/2289403/data-center/a-virtual-hit-for-mlb-advanced-media.html">running in containers</a>.</p><p>After moving to California with my family, I jumped into containers and cloud-building at <strong>Joyent</strong>. When Joyent open-sourced their <a href="https://www.joyent.com/smartos">operating system</a> and <a href="https://www.joyent.com/triton/compute">shipped that “secret sauce”</a> to large-retail and telco customers globally, I took the experience I’d gained from running it in-house, and helped other system-builders in North America, Europe, and Asia build and operate their compute-clouds.</p><p>From there, some friends and I moved to <strong>Oracle</strong>, where I gained more experience in very-large enterprise environments, compliance, and security-operations management. Many brilliant cloud-veterans re-invented the company’s entire cloud product and delivered a new, high-performance compute offering. Powering that next-gen public cloud behind the scenes is a brand new control-plane — a myriad of new services that must interoperate and be secured, monitored, and audited.</p><p>The common pattern: many of my peers and I have had success breaking down big problems into smaller, more manageable parts. What I’ve seen repeatedly is the need for these interoperating parts to trust each other. In the pursuit of performance and operability, concessions are made at the expense of security and observability:</p><ul><li>Microservices must authenticate their clients.</li><li><a href="https://blog.envoyproxy.io/service-mesh-data-plane-vs-control-plane-2774e720f7fc">Control-plane and data-plane</a> cloud services may be forced to depend upon perimeter security (like firewalls) to conduct wire-speed, unauthenticated transactions within a datacenter.</li><li>Origin servers must identify a CDN node caching for thousands of end-users, but those CDN nodes are created and destroyed frequently.</li><li>More and more, companies are managing scale and cost by running their business-critical compute jobs in dynamic infrastructure within multi-tenant public clouds. Tracking “who’s asking” and “what’s where” is difficult. Keeping access-control manageable is challenging, and relying on obscurity is not an option.</li></ul><p>As the holidays approach, I’m working on my concise answers to the questions I’m sure I’ll get from friends and family:</p><p>“So! Scytale? What do they do? What’s your job? How do you pronounce ‘Scytale’?”</p><ul><li>We help software “things” on this wild, scary internet know who’s who in a trustable, verifiable way, and then help them securely communicate with each other.</li><li>It’s my job to understand what that all that means, and to help people understand how our stuff can solve their real problems. I also drink a lot of coffee and smear up whiteboards (I’m left-handed).</li><li>We’re Scytale (we pronounce it “sigh tail”). The name is (as far as I can tell) a double-reference to ancient cryptography and “Dune”.</li></ul><p>I’m stoked for my new adventure! Find <a href="https://kccna18.sched.com/?s=spiffe&amp;iframe=no&amp;w=100%25&amp;sidebar=yes&amp;bg=false">my colleagues</a> and me at <a href="https://events.linuxfoundation.org/events/kubecon-cloudnativecon-north-america-2018/">Kubecon + CloudNativeCon</a> if you’re in Seattle next month, or <a href="https://keybase.io/ryancnelson">reach out</a> to me directly. I am pretty social; after a few years of corporate “internal and confidential” wiki posts, I love that I get to blog about this stuff again!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f35b94b28c67" width="1" height="1" alt=""><hr><p><a href="https://medium.com/scytale-io/hello-scytale-f35b94b28c67">Hello, Scytale!</a> was originally published in <a href="https://medium.com/scytale-io">Scytale.io</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>