O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

48
Jonathan CLARKE Continuous auditing for effective compliance [email protected] @jooooooon42 Co-founder & Chief Product Officer @

Transcript of O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Page 1: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Jonathan CLARKE

Continuous auditingfor effective compliance

[email protected]@jooooooon42

Co-founder &Chief Product Officer @

Page 2: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com 2

It’s a continuous world

Continuous *

Page 3: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com 3

It’s a continuous world

Integration Delivery

Improvement(agile, devops)

Continuous *

Page 4: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com 4

It’s a continuous world

adjective1. without interruption2. progressive

Synonyms: sustained, round-the-clock, relentless

Continuous

Page 5: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com 5

Continuous everything

Continuous *

Page 6: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Continuous everything

ContinuousGrowth

Continuous *

Page 7: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Continuous everything

ContinuousGrowth

ContinuouslyConnected

Continuous *

Page 8: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Continuous everything

ContinuousGrowth

ContinuousThreats

ContinuouslyConnected

Continuous *

Page 9: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Continuous everything

We need a continuous response

ContinuousGrowth

ContinuousThreats

ContinuouslyConnected

Continuous *

Page 10: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Continuous auditingfor effective compliance

Page 11: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Industryregulations

Bestpractices

CorporateregulationsLaws

Rules come from different levels

Page 12: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Industryregulations

Bestpractices

CorporateregulationsLaws

Organisationalprocess

Technicaldirectives

Rules come from different levels

Page 13: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Industryregulations

Bestpractices

CorporateregulationsLaws

Rules come from different levels

Organisationalprocess

Technicaldirectives

We can’t automatehumans!

Page 14: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Industryregulations

Bestpractices

CorporateregulationsLaws

Organisationalprocess

Technicaldirectives

Rules come from different levels

Page 15: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Examples of security technical directives

1. Auto logout after aperiod of inactivity

Page 16: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Examples of security technical directives

1. Auto logout after aperiod of inactivity

2. Password policy(strength, duration, ...)

Page 17: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Examples of security technical directives

1. Auto logout after aperiod of inactivity

2. Password policy(strength, duration, ...)

3. No compilers onproduction servers

Page 18: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Examples of security technical directives

1. Auto logout after aperiod of inactivity

2. Password policy(strength, duration, ...)

3. No compilers onproduction servers

4. Warning message onserver remote access

Page 19: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Examples of security technical directives

1. Auto logout after aperiod of inactivity

2. Password policy(strength, duration, ...)

3. No compilers onproduction servers

4. Warning message onserver remote access

5. Patch vulnerablesoftware package

Page 20: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: what and how?

Examples of security technical directives

1. Auto logout after aperiod of inactivity

2. Password policy(strength, duration, ...)

3. No compilers onproduction servers

4. Warning message onserver remote access

5. Patch vulnerablesoftware package

GOAL

Harden access

Harden access

Avoid potentialexploits

Obey the law

Avoid knownexploits

Page 21: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: traditional lifecycle

Typical lifecycle of security policy

Policy Apply onnew servers

OKRegular audits(3-12 months)

REMEDIATION

Page 22: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Security policies: traditional lifecycle

Typical lifecycle of security policy

Policy Apply onnew servers

OKRegular audits(3-12 months)?

REMEDIATION

DRIFT

Page 23: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Introducing Rudder

Rudder: nounPiece used for steering a ship.

Used to correct heading when trajectory drifts off course.

Page 24: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Introducing Rudder

Define desired state

Target

Imperative Declarative Install package xvs

Package x should be installed

Restart service zvs

Service z should be running

Copy file template y.tplvs

File y should contain line abc=def

Page 25: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Introducing Rudder

Rudder’s lifecycle

Definedesired

stateDistribute to

agents

OK

NOK

Check statelocally

OS-SpecificImplementations

Report

Page 26: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Introducing Rudder

Rudder’s continuous lifecycle

Definedesired

stateDistribute to

agents

OK

NOK

Check statelocally

OS-SpecificImplementations

Report

REPEAT

Page 27: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Introducing Rudder

High-level overview

Page 28: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Introducing Rudder

Drill-down to each individual state

Compliant

Page 29: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks can be used to check anything

Examples of security technical directives

1. Auto logout after aperiod of inactivity

2. Password policy(strength, duration, ...)

3. No compilers onproduction servers

4. Warning message onserver remote access

5. Patch vulnerablesoftware package

GOAL

Harden access

Harden access

Obey the law

Avoid potentialexploits

Avoid knownexploits

Page 30: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks can be used to check anything

Examples of security technical directives

1. Auto logout after aperiod of inactivity

2. Password policy(strength, duration, ...)

3. No compilers onproduction servers

4. Warning message onserver remote access

5. Patch vulnerablesoftware packages

GOAL

Harden access

Harden access

Obey the law

IMPLEMENTATION

File/Registryedit

File/Registryedit

Packageremove

File/Registryedit

Packageinstall/update

Avoid potentialexploits

Avoid knownexploits

Page 31: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks can be used to check anything

Photo CC BY-NC-SA 2.0 from https://www.flickr.com/photos/dillpixel/

Page 32: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks can be used to check anything

Page 33: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks can be used to check anything

Examples of security technical directives

1. Auto logout after aperiod of inactivity

GOAL

Harden access

IMPLEMENTATION

File/Registryedit

Page 34: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Avoid localexploits

Packageremove

Building blocks can be used to check anything

Examples of security technical directives

3. No compilers onproduction servers

GOAL IMPLEMENTATION

Page 35: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks in Rudder (aka generic methods)

Page 36: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks can be used to check anything

Packageabsent

Packageabsent

Security directive #2

Fileenforce

Servicerunning

Security directive #3

Packagepresent

Fileedit

Security directive #1

Page 37: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks can be used to check anything

Packageabsent

Packageabsent

Security directive #2

Fileenforce

Servicerunning

Security directive #3

Packagepresent

Fileedit

Security directive #1

RULERULE

Corporate security policy Security best practices

Page 38: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Building blocks can be used to check anything

Packageabsent

Packageabsent

Security directive #2

Fileenforce

Servicerunning

Security directive #3

Packagepresent

Fileedit

Security directive #1

Corporate security policy Security best practices

RULERULE

Page 39: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

From continuous auditing to continuous remediation

Continuous auditing

Continuous remediation

Page 40: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

From continuous auditing to continuous remediation

Rudder’s continuous lifecycle

Definedesired

stateDistribute to

agents

OK

NOK

Check statelocally

OS-SpecificImplementations

Report

REPEAT

Page 41: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

From continuous auditing to continuous remediation

Node by node Policy by policy

Page 42: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

From continuous auditing to continuous remediation

Rudder’s lifecycle with remediation

Definedesired

stateDistribute to

agents

OK

NOK

Check statelocally

OS-SpecificImplementations

Report

Remediate

REPEAT

Page 43: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

RudderOpen source

Automation & Compliance

www.rudder-project.org@RudderProject

Page 44: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

A bit more about Rudder

CloudServers

Desktop Embedded/IoT

Mobile

Any scaleTypical deployments

100s-1000s of servers.Biggest known today is 7000.

2→

> 10 000

Multi-platformMetal, virtual, cloud, …

Multi-OSC agent on UNIX/Linux,

DSC on Windows

Platform support

Page 45: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

A bit more about Rudder

APIAutomate new nodes, policy,

extract compliance

CLI / CodeCreate new configuration templates,

everyday management tasks

WebUse existing configuration

patterns, observe compliance

Separation of roles

Page 46: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Summary

Continuous IT

Continuous auditing

Continuous remediation

Page 47: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Normation – CC-BY-SAnormation.com

Summary

Fire & Forget

Worry about next thing

Continuous improvement

Page 48: O'Reilly Security - Continuous Auditing For Effective Compliance with Rudder

Thanks for listening!Any questions?

This presentation is shared under a FLOSS licence, CC-BY-SA,and available on http://www.slideshare.net/normation/.

Jonathan [email protected]

@jooooooon42Co-founder &

Chief Product Officer @