cultural change for it’s not all tech: devsecops

57
CONFIDENTIAL Designator 1 Red Hat Security Symposium Victoria, BC It’s not all tech: cultural change for DevSecOps Mike Bursell chief security architect, Red Hat OPTIONAL SECTION MARKER OR TITLE

Upload: others

Post on 16-Oct-2021

2 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

1

Red Hat Security SymposiumVictoria, BC

It’s not all tech: cultural change for DevSecOps

Mike Bursellchief security architect, Red Hat

OPTIO

NAL SECTION

MARKER O

R TITLE

Page 2: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL DesignatorAGENDA

2 Source:Insert source data hereInsert source data hereInsert source data here

Part I:

What is DevOps? And DevSecOps?

Part II:

Tools, process or culture? Which is most

important?

Summary

DevOps - more than just technology

Page 3: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

Part I:

What is DevOps?

3

Page 4: cultural change for It’s not all tech: DevSecOps

4

What is DevOps? And DevSecOps?“DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.”[1]

DESIGNBUILD

RUN

MANAGE

ADAPT

[1] https://theagileadmin.com/what-is-devops/

Page 5: cultural change for It’s not all tech: DevSecOps

5

What is DevOps? And DevSecOps?

[1] https://theagileadmin.com/what-is-devops/[2] http://www.devsecops.org/blog/2015/2/15/what-is-devsecops

“DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.”[1]

“The purpose and intent of DevSecOps is to build on the mindset that ‘everyone is responsible for security’...”[2]

DESIGNBUILD

RUN

MANAGE

ADAPT

Page 6: cultural change for It’s not all tech: DevSecOps

6

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

Page 7: cultural change for It’s not all tech: DevSecOps

7

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

“…you could have missed the last two words out.” - me

Page 8: cultural change for It’s not all tech: DevSecOps

8

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

“…you could have missed the last two words out.” - me

Classic waterfall project

DesignDevelop

TestStage

Deploy

Page 9: cultural change for It’s not all tech: DevSecOps

9

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

“…you could have missed the last two words out.” - me

Classic waterfall project

DesignDevelop

TestStage

Deploy

Security!

Page 10: cultural change for It’s not all tech: DevSecOps

10

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

“…you could have missed the last two words out.” - me

Classic waterfall project - project manager’s hope

DesignDevelop

TestStage

Deploy

Security!

Page 11: cultural change for It’s not all tech: DevSecOps

11

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

“…you could have missed the last two words out.” - me

Classic waterfall project - security architect’s guesstimate

DesignDevelop

TestStage

DeploySecurity!

Page 12: cultural change for It’s not all tech: DevSecOps

12

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

“…you could have missed the last two words out.” - me

Classic waterfall project - actual

DesignDevelop

TestStage

DeSecurity!

Page 13: cultural change for It’s not all tech: DevSecOps

13

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

“…you could have missed the last two words out.” - meDESIGN

BUILD

RUN

MANAGE

ADAPT

Page 14: cultural change for It’s not all tech: DevSecOps

14

DevOps and DevSecOps

“For 20 years, people have been leaving security till last” - colleague

“…you could have missed the last two words out.” - me

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Page 15: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

Example 1:

where the expertise lies

15

Page 16: cultural change for It’s not all tech: DevSecOps

16

“Devs and shinies”

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

(the Smaug problem)

Page 17: cultural change for It’s not all tech: DevSecOps

17

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Steps in the process

Page 18: cultural change for It’s not all tech: DevSecOps

18

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Steps in the process

Page 19: cultural change for It’s not all tech: DevSecOps

19

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Process management points● Semi-permeable membranes● Automated!● Apply policies ● Exercise governance● Log, audit

Page 20: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

Example 2:

loving your inner auditor

20

Page 21: cultural change for It’s not all tech: DevSecOps

21

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Page 22: cultural change for It’s not all tech: DevSecOps

22

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Built-in from the start; not bolted on

Page 23: cultural change for It’s not all tech: DevSecOps

23

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Built-in from the start; not bolted on

Deploy to trusted platforms with enhanced security capabilities

Page 24: cultural change for It’s not all tech: DevSecOps

24

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Built-in from the start; not bolted on

Deploy to trusted platforms with enhanced security capabilities

Automate systems with security & compliance

Page 25: cultural change for It’s not all tech: DevSecOps

25

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Built-in from the start; not bolted on

Deploy to trusted platforms with enhanced security capabilities

Automate systems with security & compliance

Revise, update, remediate as the landscape changes

Page 26: cultural change for It’s not all tech: DevSecOps

26

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Built-in from the start; not bolted on

Deploy to trusted platforms with enhanced security capabilities

Automate systems with security & compliance

Revise, update, remediate as the landscape changes

Page 27: cultural change for It’s not all tech: DevSecOps

27

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Built-in from the start; not bolted on

Deploy to trusted platforms with enhanced security capabilities

Automate systems with security & compliance

Revise, update, remediate as the landscape changes

These steps are the “most obviously” Dev and Ops

Page 28: cultural change for It’s not all tech: DevSecOps

28

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Built-in from the start; not bolted on

Deploy to trusted platforms with enhanced security capabilities

Automate systems with security & compliance

Revise, update, remediate as the landscape changes

These steps are the “most obviously” Dev and Ops

But without these steps you’re not “doing” DevOps

Page 29: cultural change for It’s not all tech: DevSecOps

29

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Revise, update, remediate as the landscape changes

Governance

Page 30: cultural change for It’s not all tech: DevSecOps

30

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Revise, update, remediate as the landscape changes

Governance

Policy

Page 31: cultural change for It’s not all tech: DevSecOps

31

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Revise, update, remediate as the landscape changes

Governance

Policy

Process

Page 32: cultural change for It’s not all tech: DevSecOps

32

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Revise, update, remediate as the landscape changes

Governance

Policy

Process

Artefacts

Page 33: cultural change for It’s not all tech: DevSecOps

33

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Revise, update, remediate as the landscape changes

Governance

Policy

Process

Artefacts

Audit

Page 34: cultural change for It’s not all tech: DevSecOps

34

Steps in the process

Security policy, process &

procedures

DESIGNBUILD

RUN

MANAGE

ADAPT

Identify security requirements & governance models

Revise, update, remediate as the landscape changes

Governance

Policy

Process

Artefacts

Audit

Page 35: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

Part II: process or culture?

Which is most important?

35

Page 36: cultural change for It’s not all tech: DevSecOps

36

It’s the culture (obviously)

Page 37: cultural change for It’s not all tech: DevSecOps

37

1. Get executive buy-in

It’s the culture (obviously)

Page 38: cultural change for It’s not all tech: DevSecOps

38

1. Get executive buy-in

2. Choose enthusiasts

It’s the culture (obviously)

Page 39: cultural change for It’s not all tech: DevSecOps

39

1. Get executive buy-in

2. Choose enthusiasts

3. Choose cross- functional team

○ (Security folks are people too!)

It’s the culture (obviously)

Page 40: cultural change for It’s not all tech: DevSecOps

40

1. Get executive buy-in

2. Choose enthusiasts

3. Choose cross- functional team

○ (Security folks are people too!)

4. Consider who might put obstacles in your way

It’s the culture (obviously)

Page 41: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

Digression!

41

Page 42: cultural change for It’s not all tech: DevSecOps

42

Not invented here● Fear of the unknown

Digression - obstacles

Page 43: cultural change for It’s not all tech: DevSecOps

43

Not invented here● Fear of the unknown

My domain● Fear of loss of control

Digression - obstacles

Page 44: cultural change for It’s not all tech: DevSecOps

44

Not invented here● Fear of the unknown

My domain● Fear of loss of control

Stuck in my ways● Fear of the new

Digression - obstacles

Page 45: cultural change for It’s not all tech: DevSecOps

45

Not invented here● Fear of the unknown

My domain● Fear of loss of control

Stuck in my ways● Fear of the new

People managers● Fear of loss of power

Digression - obstacles

Page 46: cultural change for It’s not all tech: DevSecOps

46

Not invented here● Fear of the unknown

My domain● Fear of loss of control

Stuck in my ways● Fear of the new

People managers● Fear of loss of power

Commissioning managers● Fear of loss of deadline

Digression - obstacles

Page 47: cultural change for It’s not all tech: DevSecOps

47

Not invented here● Fear of the unknown

My domain● Fear of loss of control

Stuck in my ways● Fear of the new

People managers● Fear of loss of power

Commissioning managers● Fear of loss of deadline

Unions● Fear of lack of certainty

Digression - obstacles

Page 48: cultural change for It’s not all tech: DevSecOps

48

Not invented here● Fear of the unknown

My domain● Fear of loss of control

Stuck in my ways● Fear of the new

People managers● Fear of loss of power

Commissioning managers● Fear of loss of deadline

Unions● Fear of lack of certainty

Digression - obstacles

Page 49: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

Back on track...

49

Page 50: cultural change for It’s not all tech: DevSecOps

50

1. Get executive buy-in

2. Choose enthusiasts

3. Choose cross- functional team

○ (Security folks are people too!)

4. Consider who might put obstacles in your way

5. Small feature sets per cycle

It’s the culture (obviously)

Page 51: cultural change for It’s not all tech: DevSecOps

51

1. Get executive buy-in

2. Choose enthusiasts

3. Choose cross- functional team

○ (Security folks are people too!)

4. Consider who might put obstacles in your way

5. Small feature sets per cycle

6. Expect to fail … and then succeed

It’s the culture (obviously)

Page 52: cultural change for It’s not all tech: DevSecOps

52

1. Get executive buy-in

2. Choose enthusiasts

3. Choose cross- functional team

○ (Security folks are people too!)

4. Consider who might put obstacles in your way

5. Small feature sets per cycle

6. Expect to fail … and then succeed

It’s the culture (obviously)

Page 53: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

Summary

53

Page 54: cultural change for It’s not all tech: DevSecOps

54

Summary

● DevOps allows and forces you to integrate security○ It has to part of the story, because you can’t bolt it on later

● Get the experts in○ Allow responsibilities to live in the right places

● Plan for cultural change○ Tools and processes are important too

Page 55: cultural change for It’s not all tech: DevSecOps

55

Summary

● DevOps allows and forces you to integrate security○ It has to part of the story, because you can’t bolt it on later

● Get the experts in○ Allow responsibilities to live in the right places

● Plan for cultural change○ Tools and processes are important too

Q. But where’s the definition of DevSecOps?

Page 56: cultural change for It’s not all tech: DevSecOps

56

Summary

● DevOps allows and forces you to integrate security○ It has to part of the story, because you can’t bolt it on later

● Get the experts in○ Allow responsibilities to live in the right places

● Plan for cultural change○ Tools and processes are important too

Q. But where’s the definition of DevSecOps?

A. There isn’t one: it’s a change in mindset.

Page 57: cultural change for It’s not all tech: DevSecOps

CONFIDENTIAL Designator

linkedin.com/company/red-hat

youtube.com/user/RedHatVideos

facebook.com/redhatinc

twitter.com/RedHat

57

Blog: https://aliceevebob.com/LinkedIn: https://www.linkedin.com/in/mikebursell/Twitter: @MikeCamel

Thank you

OPTIO

NAL SECTION

MARKER O

R TITLE