Greg Mosher

This guide builds on the introduction of “Security as Code”. As expected, this is the automation of security checks and gates via code and integrated into the overall DevOps process again following software engineering practices.

Use of public cloud infrastructure is now commonplace with nearly $60 billion spent annually. Of course, there are good reasons for this as Infrastructure and Platform as a Service provide several advantages over traditional in-house hosting. VerSprite shares key principles that will help you manage your cloud security risk.

In this blog post we will take a deeper dive into exactly how to approach integrating security into your Software Development LifeCycle (SDLC). In addition, we will delve into one available resource that provides guidance on how to get started.

Given the noticeable upward trend in Azure adoption, let’s explore more about Azure security, compliance, and its other rich capabilities.  In this post we’ll just touch on big picture and what is important to securing your Azure environment. 

This blog post reviews best practices and pro tips for using Amazon Web Services securely, Identity and Access Management, and the risks faced when not setup correctly.

DevOps is a fundamental shift in the way we build, test and deploy our applications and services. However, as DevOps has increased our delivery velocity, there is a real possibility that security can be left behind.

Stolen credentials remain the number one action in cybersecurity breaches. However, attackers still have other routes to your systems and data. Once you secure your AWS IAM, where do you focus next? In this piece we will look at securing AWS resources that can be attacked directly through the network.

Operating your cloud infrastructure isn’t a one-time proposition, so it makes sense that securing it isn’t either.  Establishing security compliance controls and then continuously monitoring those controls ensures your infrastructure continues to be secured per policy.