Cloud Native Data Security with OAuth

Chapter 3. Security Architecture

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the authors’ raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 3rd chapter of the final book. The GitHub repo is available at https://github.com/curityio/cloud-native-oauth-security-examples.

If you have comments about how we might improve the content and/or examples in this book, or if you notice missing material within this chapter, please reach out to the editor at [e-mail].

A good approach for an API security architecture combines the principle of separation of concerns with open standards. This way, the security architecture can scale and mature over time and you can extend it with additional functions or services when needed.

This chapter introduces a cloud native security architecture for APIs that combines identity management, API management and entitlement management with the help of the OAuth 2.0 protocol. It provides a conceptual overview of the components involved and what you need to consider when implementing API security in a cloud native environment.

What is an API Security Architecture?

An API security architecture describes the techniques that protect APIs. In a nutshell, it defines how to secure access to APIs and the data they expose. As with buildings, you need a good foundation for building an architecture. Even ...