Security | Threat Detection | Cyberattacks | DevSecOps | Compliance


Learn Microservice Authorization on Styra Academy

Styra Academy, our online training portal for free courses on OPA, Rego, and Styra Declarative Authorization Service, has a new course available - Microservice Authorization! Before diving in, let’s get a better understanding of microservices and some of the authorization challenges developers need to consider. Microservices are everywhere — and securing them presents a unique set of challenges.

How to secure microservices in a Zero-Trust environment

Microservices architecture is a convenient way to silo different software services compared to traditional software architecture and design. However, with multiple microservices communicating amongst each other - the attack surface of the network is greatly increased. The security of such a system depends on the security of all the services. Any deviation in the system’s security ultimately undermines the integrity of the entire network.

Securing Microservices-Based Apps with Dynamic Traffic Authz

Learn how to tightly control traffic flow to, from and between microservices with Styra Declarative Authorization Service (DAS) & Kong Mesh. When it comes to the digital transformation journey, teams are often faced with distributed software architectures in order to accelerate innovation and reduce costs. With Styra Declarative Authorization Service (DAS) now integrated with Kong Mesh, teams have the collaboration tools and visibility required to manage service mesh traffic via Open Policy Agent (OPA) at a global scale.

Microservices Transformed DevOps - Why Security Is Next

Microservices fundamentally changed the way we build modern applications. Before microservices, engineers had a small number of huge chunks of code that made up their application. Many apps were a single monolith of code, and some might have been broken out into a frontend, backend and database. So, when a team needed to update or patch their code, they had to do it slowly and with great care because any change to any part affected every other part of their app.

Mapping vulnerabilities to microservices with Snyk and OpsLevel

John Laban is the Founder & CEO at OpsLevel. This blog post originally appeared on the OpsLevel blog. Snyk is rapidly becoming the de facto standard for businesses that want to build security into their continuous software development processes. And with their developer-first tooling and best-in-class security intelligence, it’s no surprise.

Snyk Container meets Cloud Native Buildpacks: Cloud Native Application Security the right way

So you’re running microservices in containers? Congratulations! This is an important step towards meeting those business needs around delivering applications to the hands of your customers as soon as possible. But how can we mitigate any potential risks associated with faster software deployment? Simple, with Snyk.

Sponsored Post

When Dominoes Fall: Microservices and Distributed Systems need intelligent dataops and AI/ML to stand up tall

As soon as the ITOps technician is ready to grab a cup of coffee, a zing comes along as an alert. Cling after zing, the technician has to respond to so many alerts leading to fatigue. The question is why can’t systems be smart enough to predict bugs and fix them before sending an alert to them. And, imagine what happens when these ITOps personnel have to work with a complex and hybrid cloud of IT systems and applications. They will dive into alert fatigue.

Easily map Snyk vulnerabilities to Cortex services

Snyk is a developer-first, cloud native security platform that scans for vulnerabilities across code, dependencies, containers, and infrastructure as code. Snyk does a great job of surfacing vulnerabilities in your codebase, but it can often be challenging to map these issues back to actual services and their owners. Fortunately, Snyk’s robust API can be used to tune Snyk to integrate into solutions designed to help engineering teams understand and improve their service-oriented architecture.

5 OPA Deployment Performance Models for Microservices

If you’re responsible for a microservices app, you may be familiar with the idea of a “latency budget.” This is the maximum latency, measured as total request time, that you need for the app to work, in order to meet your SLAs and keep stakeholders happy. For a stock trading or financial services app, this budget might be the barest of microseconds.

How Microservices Impact Your App Security

An IBM survey of IT executives, developer executives, and developers found that 87% of microservices users agreed that microservices adoption is worthwhile. Microservices are popular with both technology leaders and developers, making them a highly effective tool for businesses of all sizes. Microservices have many uses, and security is one area where micro services can both help — and harm.