Spring is blooming here at PagerDuty, and so is our automation product line. We’re thrilled to share some exciting product announcements. First, we’ve officially rebranded our automation product line, Rundeck®, as PagerDuty® Process Automation. Fundamentally, everyone who buys Rundeck becomes a PagerDuty customer, so we decided to make it less confusing.

Just a few years ago, security orchestration, automation and response (SOAR) was the new buzzword associated with security modernization. Today, however, SOAR platforms are increasingly assuming a legacy look and feel. Although SOARs still have their place in a modern SecOps strategy, the key to driving SecOps forward today is no-code security automation.

In a perfect world, your Configuration Management Database (CMDB) acts as the single source of truth for all your IT device inventory and the relationships between those devices. However, maintaining accuracy is easier said than done. That’s because the traditional method for provisioning and maintaining a CMDB is complex, unwieldy, and outdated the second it's updated. To keep up with the needs of a modern CMDB, an automated discovery and dependency mapping (DDM) solution is a must.

Automation in the enterprise is nothing new. Engineers have been working with automation tools and frameworks for decades. From configuration management tools, to continuous integration and delivery pipelines to cloud formation, you name it—automation is part of the fabric of nearly any technology use case in the business landscape. If the previous statement is true, then why does automation still seem to pair with so much manual work?

There has been a rapid incline in the use of automation in many day-to-day activities, making life a bit simpler. Whether it’s through the implementation of chatbots or automated reporting tools, automation has become a new norm. It’s meant to make workloads a lot easier, as well as improve efficiency. However, not everyone may see it that way. The simple notion of automation taking over your job can cause a lot of stress, anger, and/or anxiety.

Last year, we launched functionality for users to add policy for reporting data, compliance reports, promise types, and other code as modules. With CFEngine Build, users can manage and update their own policy, the default policy and any additional modules separately. This makes it very easy to utilize policy or other modules written by the CFEngine team, or other community members. In this post we will take a look at using some modules to improve the security of our infrastructure.