The microservices architecture expands the attack surface with multiple microservices communicating with each other remotely. It’s a common principle in security that the strength of a given system is only as strong as the strength of its weakest link. Unlike in any other system design, the repercussions will be extremely highly if we do not get right the security in a microservices design. The key driving force behind microservices architecture is the speed to production (or the time to market). One should be able to introduce a change to a service, test it and instantly deploy it into production. A proper secure development lifecycle and test automation strategy needs to be there to make sure that we do not introduce security vulnerabilities at the code level. We need to have a proper plan for static code analysis and dynamic testing — and most importantly those tests should be part of the continuous delivery (CD) process. Any vulnerability should be identified early in the development lifecycle and should have shorter feedback cycles. There are multiple microservices deployment patterns — but the most commonly used one is service-per-host model. The host does not necessarily mean a physical machine — most probably it would be a container (Docker). The DevOps security needs to worry about container-level security. How do we isolate a container from other containers and what level of isolation we have between the container and the host operating system? How do we authenticate and access control users to microservices and how do we secure the communication channels between microservices? All fall under application level security. This talk addresses multiple perspectives in securing microservices: SDLC, DevOps, and application-level security.

1. INTEGRATION SUMMIT 2019
Microservices Security Landscape
Prabath Siriwardena
Vice President - Security Architecture, WSO2
INTEGRATION

2. INTEGRATION SUMMIT 2019
Monolithic

3. INTEGRATION SUMMIT 2019
Microservices

4. INTEGRATION SUMMIT 2019
Broader attack surface
Performance
Deployment complexities
Observability
Sharing user context
Polyglot architecture
Challenges

5. INTEGRATION SUMMIT 2019 5
Gateway Pattern at the Edge

6. INTEGRATION SUMMIT 2019 6
Gateway Pattern at the Edge

7. INTEGRATION SUMMIT 2019 7
Service to Service Security
Trust the Network

8. INTEGRATION SUMMIT 2019 8
Service to Service Security
Mutual TLS

9. INTEGRATION SUMMIT 2019 9
Service to Service Security
Mutual TLS + Shared JWT

10. INTEGRATION SUMMIT 2019 10
Service to Service Security
Mutual TLS + JWT (Token Exchange)

11. INTEGRATION SUMMIT 2019 11
Service to Service Security
Mutual TLS + JWT (Proxy)

12. INTEGRATION SUMMIT 2019 12
Service to Service Security
Data Plane

13. INTEGRATION SUMMIT 2019 13
Service to Service Security
Control Plane

14. INTEGRATION SUMMIT 2019 14
Service to Service Security
Authorization: Embedded PDP / Call Home

15. INTEGRATION SUMMIT 2019 15
End-to-End Flow

16. INTEGRATION SUMMIT 2019
THANK YOU
wso2.com