Security policies are increasingly complex and demanding to be implemented by operational teams. How can we be sure that our security policies are properly applied on all our servers other than through a massive and costly audit? Even if they were when they were created, how do you know if they remain perfectly compliant after a few days / weeks / months?

More generally, the problem can be generalized to a devsecops approach: how to ensure that teams work together to make system infrastructures more reliable and secure?

Discover how RUDDER, a solution based on the devops spirit that allows teams to work together, can bring its know-how during a first-hand workshop and deploy your first rules together.

In Rudder 5.0 we have introduced a plugins’ ecosystem to make Rudder more flexible and adaptable to user needs. Plugins aim to bring new functionalities to Rudder: to plug it with other tools or simply package re-usable policy sets for example. Even though the currently available plugins cover a large range of functionalities, you may need to create new ones or extend current ones to meet your specific needs.

This talk will go through the process of plugin creation and maintaining, focusing on the ones involving proper configuration elements. This will let us see the current possibilities to import, export, share and maintain subsets of configuration policies between distinct Rudder environments.