Making security automation a reality

73
Making Security Automation a Reality September 2011 Tuesday, September 20, 11

description

I believe we can distill our collective security reality down to a few key points or issues, and we’ll visit each one (quickly). This information, coupled with an assertion leads to a single question: Why are we, as an information security industry, falling behind? The Answer: I’ll take you through what that answer means from the perspective of the information security industry and our tools in general.The Solution: There may, in fact, be a solution well on its way in our industry – it’s just not quite there yet. I’ll provide some insight to what exists, its shortcomings, and finally, how you can help make a difference.

Transcript of Making security automation a reality

Page 1: Making security automation a reality

Making Security Automation a RealitySeptember 2011

Tuesday, September 20, 11

Page 2: Making security automation a reality

If you get anything out of this at all...

Tuesday, September 20, 11

Page 3: Making security automation a reality

If you get anything out of this at all...

We are falling behind...

Tuesday, September 20, 11

Page 4: Making security automation a reality

If you get anything out of this at all...

But we don’t have to

Tuesday, September 20, 11

Page 5: Making security automation a reality

Expectations

• Approach some realities

• The Question

• The Answer

• The Solution

Tuesday, September 20, 11

Page 6: Making security automation a reality

Information Security

Tuesday, September 20, 11

Page 7: Making security automation a reality

Information Security

• The protection of information and information systems from unauthorized access, use, disruption, modification or destruction.

Tuesday, September 20, 11

Page 8: Making security automation a reality

Rudiments

Tuesday, September 20, 11

Page 9: Making security automation a reality

Rudiments• Confidentiality

Tuesday, September 20, 11

Page 10: Making security automation a reality

Rudiments• Confidentiality

• Integrity

Tuesday, September 20, 11

Page 11: Making security automation a reality

Rudiments• Confidentiality

• Integrity

• Availability

Tuesday, September 20, 11

Page 12: Making security automation a reality

Threat Taxonomy

Tuesday, September 20, 11

Page 13: Making security automation a reality

Threat Agent Evolution

Tuesday, September 20, 11

Page 14: Making security automation a reality

System Complexity

Tuesday, September 20, 11

Page 15: Making security automation a reality

Situational Security

Tuesday, September 20, 11

Page 16: Making security automation a reality

Scarce Resources

Tuesday, September 20, 11

Page 17: Making security automation a reality

Business Matters

Tuesday, September 20, 11

Page 18: Making security automation a reality

Our Reality

Tuesday, September 20, 11

Page 19: Making security automation a reality

Our Reality

• Immutable rudiments: CIA

Tuesday, September 20, 11

Page 20: Making security automation a reality

Our Reality

• Immutable rudiments: CIA

• Threat taxonomies: Relevant but outdated

Tuesday, September 20, 11

Page 21: Making security automation a reality

Our Reality

• Immutable rudiments: CIA

• Threat taxonomies: Relevant but outdated

• Threat Agent evolution

Tuesday, September 20, 11

Page 22: Making security automation a reality

Our Reality

• Immutable rudiments: CIA

• Threat taxonomies: Relevant but outdated

• Threat Agent evolution

• System complexity continues increase

Tuesday, September 20, 11

Page 23: Making security automation a reality

Our Reality

• Immutable rudiments: CIA

• Threat taxonomies: Relevant but outdated

• Threat Agent evolution

• System complexity continues increase

• Rapid change in situational security

Tuesday, September 20, 11

Page 24: Making security automation a reality

Our Reality

• Immutable rudiments: CIA

• Threat taxonomies: Relevant but outdated

• Threat Agent evolution

• System complexity continues increase

• Rapid change in situational security

• Severe shortage of security professionals

Tuesday, September 20, 11

Page 25: Making security automation a reality

Our Reality

• Immutable rudiments: CIA

• Threat taxonomies: Relevant but outdated

• Threat Agent evolution

• System complexity continues increase

• Rapid change in situational security

• Severe shortage of security professionals

• Security needs alignment with business process

Tuesday, September 20, 11

Page 26: Making security automation a reality

Why Do We Fall Behind?

Tuesday, September 20, 11

Page 27: Making security automation a reality

Why Do We Fall Behind?

• Too many points of human touch

Tuesday, September 20, 11

Page 28: Making security automation a reality

Why Do We Fall Behind?

• Too many points of human touch

• Too many smart people working on the mundane

Tuesday, September 20, 11

Page 29: Making security automation a reality

Why Do We Fall Behind?

• Too many points of human touch

• Too many smart people working on the mundane

• We work from information, not knowledge

Tuesday, September 20, 11

Page 30: Making security automation a reality

Industry Requirements

Tuesday, September 20, 11

Page 31: Making security automation a reality

Industry Requirements

• Ability to convey knowledge

Tuesday, September 20, 11

Page 32: Making security automation a reality

Industry Requirements

• Ability to convey knowledge

• Common representation of concepts

Tuesday, September 20, 11

Page 33: Making security automation a reality

Industry Requirements

• Ability to convey knowledge

• Common representation of concepts

• Ability to reason over information

Tuesday, September 20, 11

Page 34: Making security automation a reality

Industry Requirements

• Ability to convey knowledge

• Common representation of concepts

• Ability to reason over information

• Enable dynamic proaction

Tuesday, September 20, 11

Page 35: Making security automation a reality

Put it together

Tuesday, September 20, 11

Page 36: Making security automation a reality

Put it together

Conveying knowledge about common concepts between tools with the ability to reason frees security personnel

from repetitive, mundane tasks and allows them to focus on what matters: dynamic proaction.

Tuesday, September 20, 11

Page 37: Making security automation a reality

A solution Exists

Tuesday, September 20, 11

Page 38: Making security automation a reality

A solution ExistsSort of...

Tuesday, September 20, 11

Page 39: Making security automation a reality

Security Automation Standards

Tuesday, September 20, 11

Page 40: Making security automation a reality

The General Idea

Tuesday, September 20, 11

Page 41: Making security automation a reality

The General Idea

Tuesday, September 20, 11

Page 42: Making security automation a reality

The Good

• Protocols

• Enumerations

• Languages

• Metrics

Tuesday, September 20, 11

Page 43: Making security automation a reality

The Bad

• Lack of Governance

• Lack of rigor

• Model issues

Tuesday, September 20, 11

Page 44: Making security automation a reality

The Ugly

• They just keep on keeping on...

• Politics

Tuesday, September 20, 11

Page 45: Making security automation a reality

One More Good

• The bad and the ugly are changing for the better starting RIGHT NOW.

Tuesday, September 20, 11

Page 46: Making security automation a reality

Needed Change

Tuesday, September 20, 11

Page 47: Making security automation a reality

Needed Change

• Still too static

Tuesday, September 20, 11

Page 48: Making security automation a reality

Needed Change

• Still too static

• Not cohesive

Tuesday, September 20, 11

Page 49: Making security automation a reality

Needed Change

• Still too static

• Not cohesive

• Differing views of the world

Tuesday, September 20, 11

Page 50: Making security automation a reality

The End Game

Tuesday, September 20, 11

Page 51: Making security automation a reality

Enterprise SimulationIf we want to react to new attack vectors and threats in a dynamic manner, then we must accurately simulate system state, events, and the attacks against them.

Tuesday, September 20, 11

Page 52: Making security automation a reality

Enterprise SimulationIf we want to react to new attack vectors and threats in a dynamic manner, then we must accurately simulate system state, events, and the attacks against them.

File systems & permissions

Platform configuration items

Network stack configuration

Host and network services

Ports & Protocols

Host hardware configuration

Process maps

Tuesday, September 20, 11

Page 53: Making security automation a reality

Enterprise SimulationIf we want to react to new attack vectors and threats in a dynamic manner, then we must accurately simulate system state, events, and the attacks against them.

File systems & permissions

Platform configuration items

Network stack configuration

Host and network services

Ports & Protocols

Host hardware configuration

Process maps

Compliance frameworks

Security Concepts

Security Contexts

Cryptographic Primitives

Measurements for strength

Asset Identification

Reporting

Tuesday, September 20, 11

Page 54: Making security automation a reality

Requirements Redux

Tuesday, September 20, 11

Page 55: Making security automation a reality

Requirements Redux

• Ability to convey knowledge

Tuesday, September 20, 11

Page 56: Making security automation a reality

Requirements Redux

• Ability to convey knowledge

• Common representation of concepts

Tuesday, September 20, 11

Page 57: Making security automation a reality

Requirements Redux

• Ability to convey knowledge

• Common representation of concepts

• Ability to reason over information

Tuesday, September 20, 11

Page 58: Making security automation a reality

Requirements Redux

• Ability to convey knowledge

• Common representation of concepts

• Ability to reason over information

• Enable dynamic proaction

Tuesday, September 20, 11

Page 59: Making security automation a reality

Requirements Redux

• Ability to convey knowledge

• Common representation of concepts

• Ability to reason over information

• Enable dynamic proaction

• Reduce code changes

Tuesday, September 20, 11

Page 60: Making security automation a reality

Example: Relationships

Tuesday, September 20, 11

Page 61: Making security automation a reality

Example: Attack method discovery

Tuesday, September 20, 11

Page 62: Making security automation a reality

Recommendations

Tuesday, September 20, 11

Page 63: Making security automation a reality

Recommendations• Refocus compliance to focus on security

Tuesday, September 20, 11

Page 64: Making security automation a reality

Recommendations• Refocus compliance to focus on security

• Define relationships between and within models

Tuesday, September 20, 11

Page 65: Making security automation a reality

Recommendations• Refocus compliance to focus on security

• Define relationships between and within models

• Move to knowledge-based technologies

Tuesday, September 20, 11

Page 66: Making security automation a reality

Recommendations• Refocus compliance to focus on security

• Define relationships between and within models

• Move to knowledge-based technologies

• Emphasize concepts and their relationships

Tuesday, September 20, 11

Page 67: Making security automation a reality

Recommendations• Refocus compliance to focus on security

• Define relationships between and within models

• Move to knowledge-based technologies

• Emphasize concepts and their relationships

• Emphasize machine reasoning

Tuesday, September 20, 11

Page 68: Making security automation a reality

Recommendations• Refocus compliance to focus on security

• Define relationships between and within models

• Move to knowledge-based technologies

• Emphasize concepts and their relationships

• Emphasize machine reasoning

• Emphasize dynamic content w/o code change

Tuesday, September 20, 11

Page 69: Making security automation a reality

Recommendations• Refocus compliance to focus on security

• Define relationships between and within models

• Move to knowledge-based technologies

• Emphasize concepts and their relationships

• Emphasize machine reasoning

• Emphasize dynamic content w/o code change

• Investigate “Big Data” Technologies

Tuesday, September 20, 11

Page 70: Making security automation a reality

Recommendations• Refocus compliance to focus on security

• Define relationships between and within models

• Move to knowledge-based technologies

• Emphasize concepts and their relationships

• Emphasize machine reasoning

• Emphasize dynamic content w/o code change

• Investigate “Big Data” Technologies

• Especially Semantic Web Technologies

Tuesday, September 20, 11

Page 71: Making security automation a reality

Call To Action

• Everyone here is a stakeholder

• Your voice can be heard

• Participate, participate, participate

• http://scap.nist.gov

Tuesday, September 20, 11

Page 72: Making security automation a reality

Questions?

Tuesday, September 20, 11