Dynamic Policy Enforcement for Privacy Techniques in Microservice Architectures
summary
Prototype integrates data minimisation and purpose limitation into gRPC using a gRPC interceptor that validates JWT per-call claims and transforms responses before they reach services. Policy enforcement maps data categories to purposes via a PAP/PDP/PEP model so shipping vs billing fields get masked, generalized, suppressed or truncated. Implementation runs in a cloud-native microservice environment, demonstrates practicality with reasonable overheads but measurable latency impact that needs further optimisation.
AI-written summary · about
chapters (8)
- 0:00Privacy in microservices
- 2:11Legislative context
- 6:03Data minimization in gRPC
- 9:38Privacy techniques
- 12:26Privacy with gRPC interceptors
- 16:20Dynamic policy enforcement
- 18:27Performance impact
- 20:16Q&A
related talks
23mMicroservice Security at the API Level
39mMicroservice Security via MicroProfile JWT
23mAuthentication and Authorization in Micro Services
51mStateless Microservice Security via JWT, TomEE and MicroProfile
49mSecurity & Trust in a Microservices World
31mAuthentication and Security in gRPC Microservices
15mSafeTree: Expressive Tree Policies for Microservices
01h 02mPractical Microservice Security