Configurations: Do you prove yours ? Continuous configuration, - PowerPoint PPT Presentation

Pass The SALT 2019 Configurations: Do you prove yours ? Continuous configuration, observability, compliance Pass the SALT 2019 Alexandre BRIANCEAU alexandre@rudder.io @abrianceau

How are the servers doing? Pass The SALT 2019 No error nor change in logs means success? Aren’t we missing something?

Main challenges faced nowadays Pass The SALT 2019 Multiple teams, diluted expertise, harder reporting MGMT DEV SEC OPS EXTERN DEV QA PRODUCTION RECOVERY Heterogeneous systems, reduced visibility, ease of use and understanding 3

Getting and understanding the info is complex Pass The SALT 2019 Operators, Managers, Experts, APIs have differents needs Frustration if we need a third party to get data We mistrust what we don’t understand

Definition Pass The SALT 2019 “ Configuration management is a systems engineering process for establishing and maintaining consistency of a product [...] throughout its life. Configuration_management

How DevSecOps can help to understand? Pass The SALT 2019 Culture Share Automation Measure

Let's remember: What does configuration management do? Pass The SALT 2019 configuration feedback configuration target state

Let's remember: What does configuration management do? Pass The SALT 2019 configuration feedback configuration target state configuration feedback configuration feedback

Definition (again) Pass The SALT 2019 “ Observability is a measure of how well internal states of a system can be inferred from knowledge of its external outputs . Observability

Monitoring VS Observability: having a factual & deep insight Pass The SALT 2019 VS monitoring observability

Why we need Observability in Configuration Management? Pass The SALT 2019 A B Causality Perspective Agency trust and prove provide insights help teams find configuration states relevant to different needs the best levers for their job

Let’s take an implementation example... Pass The SALT 2019

These concepts are core to Rudder Pass The SALT 2019 Everyone/thing can be an actor of configuration management

Observability and how Rudder can prove the compliance? Pass The SALT 2019 Environmental context Event logs Historisation NODE RUDDER config RULE DIRECTIVE GROUP (global) ● Properties PARAM ● Id ● Id ● Id ● Policy Mode ● Policy Mode ● (Components) ● Schedule... ● Schedule... Historisation Change request Node configuration RUN Get config ● Id : . . . Files RUN ● Generated : . . . ● Reports ● Reports ● Reports ● ... ● Reports Metadata Send expected reports ● ... ● ... ● Integrity Historisation ● ... ● Signature METADATA ● node id METADATA Send configuration Expected reports Run reports Config reports ● config id ● node id (node id, config id, ● For Rule R , ● run timestamp timestamp) ● config id Directive D1 , ● run timestamp Component C ● Signature Compliance historised

French, mature and open-source of Pass The SALT 2019 continuous configuration compliance Manage OS, middleware and software level Team oriented (WebUI, CLI, API) Audit only or automatic drift remediation Continuous reporting and dashboarding

Thank you ! Pass The SALT 2019 Any questions ? 5mn Survey on SecOps: bit.ly/pts19-secops Pass the SALT 2019 Alexandre BRIANCEAU alexandre@rudder.io @abrianceau